From: Matt Fleming <matt@codeblueprint.co.uk>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Matt Fleming <matt.fleming@intel.com>,
Kees Cook <keescook@chromium.org>,
Junjie Mao <eternal.n08@gmail.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] x86, boot: Allow 64bit EFI kernel to be loaded above 4G
Date: Wed, 25 Feb 2015 12:57:44 +0000 [thread overview]
Message-ID: <20150225125744.GE9758@codeblueprint.co.uk> (raw)
In-Reply-To: <CAE9FiQW8qRw76Q9R0YqmXVPC_scNNYc440_XoDVrLNRc+OxOhQ@mail.gmail.com>
On Tue, 24 Feb, at 04:31:27PM, Yinghai Lu wrote:
> On Tue, Feb 24, 2015 at 1:55 PM, Matt Fleming <matt@codeblueprint.co.uk> wrote:
> > On Sun, 22 Feb, at 07:43:48PM, Yinghai Lu wrote:
> >> +Field name: ext_code32_start
> >> +Type: modify (optional, reloc)
> >> +Offset/size: 0x268/4
> >> +Protocol: 2.14+
> >> +
> >> + This field is the upper 32bits of load address when EFI 64bit kernel
> >> + is loaded above 4G. And it is used with code32_start to compare to
> >> + pref_address to decide if kernel need to be relocated further.
> >
> > I think we can delete the second sentence.
> >
> > But these are minimal changes and I'm happy to fix them up when applying
> > this patch if that's OK?
>
> Sure. Please go ahead.
Applied, thanks Yinghai.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-02-25 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 3:43 [PATCH v2] x86, boot: Allow 64bit EFI kernel to be loaded above 4G Yinghai Lu
2015-02-24 21:55 ` Matt Fleming
2015-02-25 0:31 ` Yinghai Lu
2015-02-25 12:57 ` Matt Fleming [this message]
2015-02-25 10:31 ` Ingo Molnar
2015-02-25 12:57 ` Matt Fleming
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=20150225125744.GE9758@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=corbet@lwn.net \
--cc=eternal.n08@gmail.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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