linux-kernel - Re: [PATCH] x86, boot: Allow 64bit EFI kernel to be loaded above 4G

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAE9FiQWjvVLbXVKCvi1aUn89eg3Y_1yxN+uTN0mBDJw0sAYO1w@mail.gmail.com>
Date:	Wed, 18 Feb 2015 11:47:01 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Baoquan He <bhe@...hat.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86, boot: Allow 64bit EFI kernel to be loaded above 4G

On Wed, Feb 18, 2015 at 3:29 AM, Baoquan He <bhe@...hat.com> wrote:
> On 02/17/15 at 11:22pm, Yinghai Lu wrote:
>> On Tue, Feb 10, 2015 at 10:11 PM, Baoquan He <bhe@...hat.com> wrote:
> I am sorry I didn't get what you mean. I have tried to set another ident
> mapping for new range and it is successful seeing from debug message
> printing. However it always reboot because of GPF. That's why I made
> that small debug patch which add another 4G ident mapping and hardcoded
> to put kernel between 4G and 8G.
>
> Could you say more of it?  Or which direction should I go?

I would suggest:
leave physical address random handling to bootloader, as bootloader always
need to set ident mapping to cover kernel/bootparam/cmdline.

For virtual address random handling it should go kasl in kernel.

Thanks

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