Messages in this thread | | | Date | Mon, 25 Feb 2019 10:39:51 +0100 | From | Borislav Petkov <> | Subject | Re: [PATCHv7] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr |
| |
On Sun, Feb 24, 2019 at 09:25:18PM +0800, Pingfan Liu wrote: > Maybe I misunderstood you, but does "requested range failed" mean that > user specify the range? If yes, then it should be the duty of user as > you said later, not the duty of kernel"
No, it should say that it selected a different range only when the user didn't specify it. Which would mean that the user didn't care about the range - she/he only wanted to have *any* crashkernel range reserved. I.e., crashkernel=X invocation.
> We do not know the memory layout of a system, maybe a system with > memory less than 4GB. So it is better to try all the range of system > memory.
Ok. If 4G fails, you set high and then try again.
-- Regards/Gruss, Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
| |