From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: 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,
dyoung@redhat.com
Subject: [PATCH v2 1/2] x86/efi/64: Clean up code comment about efi region
Date: Wed, 8 Mar 2017 18:45:57 +0800 [thread overview]
Message-ID: <20170308104557.GE6570@x1> (raw)
In-Reply-To: <1488959258-4731-1-git-send-email-bhe@redhat.com>
EFI allocates runtime services regions starting from EFI_VA_START, -4G,
decrement to EFI_VA_END. So remove the bottom-up term to avoid confusion.
Signed-off-by: Baoquan He <bhe@redhat.com>
---
arch/x86/platform/efi/efi_64.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/x86/platform/efi/efi_64.c b/arch/x86/platform/efi/efi_64.c
index a4695da..e941b29 100644
--- a/arch/x86/platform/efi/efi_64.c
+++ b/arch/x86/platform/efi/efi_64.c
@@ -47,8 +47,9 @@
#include <asm/pgalloc.h>
/*
- * We allocate runtime services regions bottom-up, starting from -4G, i.e.
- * 0xffff_ffff_0000_0000 and limit EFI VA mapping space to 64G.
+ * We allocate runtime services regions starting from -4G, i.e.
+ * 0xffff_ffff_0000_0000 and decrement as we go. The EFI VA mapping space
+ * is limited to 64G.
*/
static u64 efi_va = EFI_VA_START;
--
2.5.5
prev parent reply other threads:[~2017-03-08 12:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 7:47 [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment 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 ` [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment Dave Young
2017-03-08 8:45 ` 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 ` Baoquan He [this message]
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=20170308104557.GE6570@x1 \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dyoung@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