Messages in this thread | | | Date | Mon, 25 Feb 2019 12:30:03 +0100 | From | Borislav Petkov <> | Subject | Re: [PATCHv7] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr |
| |
On Mon, Feb 25, 2019 at 07:12:16PM +0800, Dave Young wrote: > If we move to high as default, it will allocate 160M high + 256M low. It
We won't move to high by default - we will *fall* back to high if the default allocation fails.
> To make the process less fragile maybe we can remove the 896M limitation > and only try <4G then go to high.
Sure, the more robust for the user, the better.
-- Regards/Gruss, Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
| |