From: Baoquan He <bhe@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86, boot: Allow 64bit EFI kernel to be loaded above 4G
Date: Wed, 18 Feb 2015 19:29:56 +0800 [thread overview]
Message-ID: <20150218112956.GA1965@dhcp-17-102.nay.redhat.com> (raw)
In-Reply-To: <CAE9FiQVbuQ+qMn+-V0jDQ9AomR5-k68utXdprbMhAXvXWYzd7w@mail.gmail.com>
On 02/17/15 at 11:22pm, Yinghai Lu wrote:
> On Tue, Feb 10, 2015 at 10:11 PM, Baoquan He <bhe@redhat.com> wrote:
> > Hi Yinghai,
> >
> > Could you please help to have a look at a problem which I encountered?
> >
> > I am trying to make kaslr randomize on both kernel physical and virtual
> > address separately. Now the separate randomization has been done,
> > kernel physical address can be randomized to [16M, 4G], and virtual
> > address can be randomzed to [16M, 1G]. Below is the post.
> > http://thread.gmane.org/gmane.linux.kernel/1870532
> >
> > Now I am trying to make kernel physical address randomize anywhere, not
> > limited to below 4G. As you know in arch/x86/boot/compressed/head_64.S a
> > identity mapping of 0~4G has been built, for address above 4G I added an
> > IDT and #PF handler. Then I hardcoded the output address of
> > choose_kernel_location as 5G, the #PF handler worked, however it will
> > reboot in arch/x86/kernel/head_64.S.
>
> For 64bit, I'd like to see bootloader could load kernel to random hw address.
>
> otherwise you will need to set another ident mapping for new range.
Hi Yinghai,
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?
Thanks a lot for your help!
Thanks
Baoquan
>
> Thanks
>
> Yinghai
next prev parent reply other threads:[~2015-02-18 11:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 2:03 Yinghai Lu
2015-02-05 3:25 ` Dave Young
2015-02-05 5:25 ` Yinghai Lu
2015-02-05 6:09 ` Dave Young
2015-02-18 7:29 ` Yinghai Lu
2015-02-09 18:27 ` Matt Fleming
2015-02-09 20:23 ` Yinghai Lu
2015-02-11 15:55 ` Matt Fleming
2015-02-11 16:29 ` Peter Jones
2015-02-12 14:59 ` Matt Fleming
2015-02-11 6:11 ` Baoquan He
2015-02-18 7:22 ` Yinghai Lu
2015-02-18 11:29 ` Baoquan He [this message]
2015-02-18 19:47 ` Yinghai Lu
2015-02-20 2:13 ` Baoquan He
2015-02-20 3:35 ` Yinghai Lu
2015-02-20 9:28 ` Baoquan He
2015-02-20 23:53 ` Yinghai Lu
2015-02-21 2:49 ` Baoquan He
2015-02-21 20:00 ` Yinghai Lu
2015-02-22 13:18 ` Baoquan He
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150218112956.GA1965@dhcp-17-102.nay.redhat.com \
--to=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®