[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f355e26eead641f5f281372aadf9dee7de19a4c7.camel@physik.fu-berlin.de>
Date: Tue, 27 Aug 2024 08:37:22 +0200
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: Baoquan He <bhe@...hat.com>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>, Dave Vasilevsky
<dave@...ilevsky.ca>, linuxppc-dev@...ts.ozlabs.org,
linux-sh@...r.kernel.org, mpe@...erman.id.au, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org, Reimar Döffinger
<Reimar.Doeffinger@....de>
Subject: Re: [PATCH] crash: Default to CRASH_DUMP=n when support for it is
unlikely
On Tue, 2024-08-27 at 14:22 +0800, Baoquan He wrote:
> About why it's enabled by default, as Michael has explained in another
> thread, distros usualy needs to enable it by default because vmcore
> dumping is a very important feature on servers, even guest instances.
> Even though kdump codes are enabled to built in, not providing
> crashkernel= value won't make vmcore dumping take effect, it won't cost
> system resources in that case.
OK, thanks for the explanation. But as we have found out in the mean time,
the assumption was wrong to enable it by default for all architectures as
some architectures cannot boot a crash dump kernel with their default bootloader
but only through kexec.
Can we have a follow-up patch to disable crash dump kernels where they're
not needed? I mean, not every platform supported by Linux is obviously a
x86-based or POWER-based server.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Powered by blists - more mailing lists