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

From: Yinghai Lu
Date: Wed Mar 04 2015 - 19:12:53 EST


On Wed, Mar 4, 2015 at 1:35 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> On Wed, Mar 4, 2015 at 7:39 AM, Baoquan He <bhe@xxxxxxxxxx> wrote:
>>
>> I got the reason and made a debug patch to fix it. Could you please
>> apply it on top of this patchset and try again? Then it will behave well
>> and just return 0x13c000000 since no random is got.
>
> random_base can not be move down?
>

Modify the min_addr will allow move down, and it is safe as we put all
related into mem_avoid now.


kernel: read done [ linux 9.55MiB 100% 7.26MiB/s ]
params: [13fffc000,13fffffff]
cmdline: [13fffb000,13fffb7fe]
kernel: [13c000000,13f394fff]
initrd: [139d7c000,13bfff7e3]
initrd: read 1 file done [ initrd.img 34.51MiB 100% 11.39MiB/s ]
early console in decompress_kernel
decompress_kernel:
input: [0x13e9ee3b4-0x13f36b9df], output: [0x13c000000-0x13f394fff],
heap: [0x13f376ac0-0x13f37eabf]
boot via startup_64
KASLR using RDTSC...
KASLR using RDTSC...
new output: [0x6f000000-0x72394fff]

Decompressing Linux... xz... Parsing ELF... Performing relocations... done.
Booting the kernel.
[ 0.000000] bootconsole [uart0] enabled
[ 0.000000] Kernel Layout:
[ 0.000000] .text: [0x6f000000-0x70096a9c]
[ 0.000000] .rodata: [0x70200000-0x70a4efff]
[ 0.000000] .data: [0x70c00000-0x70e4e9bf]
[ 0.000000] .init: [0x70e50000-0x7120bfff]
[ 0.000000] .bss: [0x71219000-0x7234efff]
[ 0.000000] .brk: [0x7234f000-0x72374fff]


Please check

https://git.kernel.org/cgit/linux/kernel/git/yinghai/linux-yinghai.git/log/?h=for-x86-4.0-rc2-aslr

for updated patches.

Your patches still have some format warning, Please use
./scripts/checkpatch.pl
to find them and fix them before next post.

Also patch should have "x86,kasl" in the title.

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/