On Thu, Feb 19, 2015 at 6:13 PM, Baoquan He <b...@redhat.com> wrote: > On 02/18/15 at 11:47am, Yinghai Lu wrote: > > Kaslr need both virtual and physical address be randomized, otherwise > it doesn't make sense. Please check what hpa said about this issue: > > https://lkml.org/lkml/2014/10/13/350 >
If I read correctly, it could be separated. phy one could be on bootloader and virtual could be in kernel. > And usually no bootloader often load kernel onto a random physical > address. Fow now we can often see kexec/kdump did this. I believe Kees > introduced kaslr to mainly solve security issue of normal kernel which > is not like kexec/kdump for testing or debugging. Randomizing physical > address makes sense for kaslr feature. I put some grub2 patches that extend grub2 to load kernel/initrd above 4G into github tree. https://github.com/yhlu/grub2.git main purpose for that feature is to handle initrd that bigger than 4G. or you can try you solution on system that have 64bit EFI support, then you will don't need to worry about set ident mapping even. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/