Re: [PATCHv7] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jan 25, 2019 at 09:45:18PM +0800, Dave Young wrote:
> AFAIK, some people prefer to explictly reserve crash memory at high
> region even if it is possible to reserve at low area.  May because
> <4G memory is limited on large server, they want to leave this for other
> use. 
> 
> Yinghai or Vivek should know more about the history, probably they can
> recall some initial reason.

Yes, just "prefer" is not good enough. There should be a technical
reason why that's there.

Also, if the user doesn't care, then the code should be free to force
"high" and thus probe a different range for allocation.

> Good question, still it may be some historical reason, but it is good to
> make them clear and rethink about it after long time.
> 
> I also want to understand, need dig the log more.

Good idea. That would be a very nice cleanup. :-)

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

_______________________________________________
kexec mailing list
kexec@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/kexec



[Index of Archives]     [LM Sensors]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux