From: Dave Young <dyoung@redhat.com>
To: Baoquan He <bhe@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
thgarnie@google.com, keescook@chromium.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment
Date: Wed, 8 Mar 2017 16:18:12 +0800 [thread overview]
Message-ID: <20170308081812.GA12600@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <1488959258-4731-1-git-send-email-bhe@redhat.com>
On 03/08/17 at 03:47pm, Baoquan He wrote:
> EFI allocate runtime services regions down from EFI_VA_START, -4G.
> It should be top-down handling.
>
> Signed-off-by: Baoquan He <bhe@redhat.com>
> ---
> arch/x86/platform/efi/efi_64.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/platform/efi/efi_64.c b/arch/x86/platform/efi/efi_64.c
> index a4695da..6cbf9e0 100644
> --- a/arch/x86/platform/efi/efi_64.c
> +++ b/arch/x86/platform/efi/efi_64.c
> @@ -47,7 +47,7 @@
> #include <asm/pgalloc.h>
>
> /*
> - * We allocate runtime services regions bottom-up, starting from -4G, i.e.
> + * We allocate runtime services regions top-down, starting from -4G, i.e.
Baoquan, I think original bottom-up is right, it is just considering
-68G as up, see the x86_64 mm.txt. We regard vmalloc as higher address
although from mathematics view it is lower then positive addresses.
> * 0xffff_ffff_0000_0000 and limit EFI VA mapping space to 64G.
> */
> static u64 efi_va = EFI_VA_START;
> --
> 2.5.5
>
Thanks
Dave
next prev parent reply other threads:[~2017-03-08 8:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 7:47 Baoquan He
2017-03-08 7:47 ` [PATCH 2/2] x86/mm/KASLR: Correct the upper boundary of KALSR mm regions if adjacent to EFI Baoquan He
2017-03-08 8:18 ` Dave Young
2017-03-08 8:35 ` Bhupesh Sharma
2017-03-08 15:32 ` Thomas Garnier
2017-03-15 6:13 ` Baoquan He
2017-03-15 6:31 ` Baoquan He
2017-03-08 8:18 ` Dave Young [this message]
2017-03-08 8:45 ` [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment Baoquan He
2017-03-08 8:54 ` Borislav Petkov
2017-03-08 9:08 ` Baoquan He
2017-03-09 1:38 ` Dave Young
2017-03-08 9:00 ` Bhupesh Sharma
2017-03-08 9:09 ` Baoquan He
2017-03-08 9:35 ` Borislav Petkov
2017-03-08 10:17 ` Baoquan He
2017-03-08 10:50 ` Borislav Petkov
2017-03-09 0:48 ` Dave Young
2017-03-08 20:05 ` Bhupesh Sharma
2017-03-08 9:45 ` Baoquan He
2017-03-08 10:45 ` [PATCH v2 1/2] x86/efi/64: Clean up code comment about efi region 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=20170308081812.GA12600@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=x86@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®