* Chao Fan <fanc.f...@cn.fujitsu.com> wrote: > Long time no reply, rebase the patchset, change the parameter name > from 'kaslr_mem' to 'kaslr_boot_mem'. There's no more code change. > > ***Background: > People reported that kaslr may randomly chooses some positions > which are located in movable memory regions. This will break memory > hotplug feature.
[...] > ***Solutions: > Introduce a new kernel parameter 'kaslr_boot_mem=nn@ss' to let users to > specify the memory regions where kernel can be allowed to randomize > safely. Manual solutions like that are pretty suboptimal to users, aren't they? In what way does memory hotplug feature 'break'? Does it crash or misbehave? Or simply does it not allow the movement of the affected memory region, while still allowing the rest to be moved? Thanks, Ingo