Re: [PATCH v2 7/9] get the random phy addr according to slot_area info

[Yinghai Lu]

On Tue, Mar 3, 2015 at 3:42 AM, Baoquan He <bhe@xxxxxxxxxx> wrote:
>
> Here input means the region where kernel was linked to load?
>
> In normal kernel the linked address is 0x1000000. In your input region
> the result of ALIGN(0x13f5ed3b4, CONFIG_PHYSICAL_ALIGN) is 0x140000000.
> And size of this region is smaller than 16M. It should return in
> process_e820_entry() with two checks.
>
> I guess you use kexec or a special bootloader to put kernel in this
> load address.
>


with patched grub2 that load kernel/initrd/param/cmdline etc above 4G.

kernel: read done                           [ linux  9.55MiB  100%  7.25MiB/s ]
params: [13fffc000,13fffffff]
cmdline: [13fffb000,13fffb7fe]
kernel: [13c000000,13f38cfff]
initrd: [139d7c000,13bfff7e3]
initrd: read 1 file done             [ initrd.img  34.51MiB  100%  11.17MiB/s ]
early console in decompress_kernel
KASLR using RDTSC...
decompress_kernel:
  input: [0x13e9ed3b4-0x13f36a64b], output: 0x16c000000, heap:
[0x13f376000-0x13f37dfff]

Decompressing Linux... xz...

XZ-compressed data is corrupt

 -- System halted

13c000000 is loaded address.
0x13e9ed3b4 is the copied address, and decompress_kernel will use it as input.
output is back to 13c000000 if aslr is not used.

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/