From: Baoquan He <bhe@redhat.com>
To: Borislav Petkov <bp@suse.de>
Cc: Dave Young <dyoung@redhat.com>,
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 17:08:33 +0800 [thread overview]
Message-ID: <20170308090833.GA6570@x1> (raw)
In-Reply-To: <20170308085447.pt55rref5eqmuf5x@pd.tnic>
On 03/08/17 at 09:54am, Borislav Petkov wrote:
> On Wed, Mar 08, 2017 at 04:45:13PM +0800, Baoquan He wrote:
> > -4G and -68G just a trick which makes people understand easily, still we
> > think kernel text mapping region is in higher addr area then vmalloc. I
> > personnally think.
>
> Just remove the direction: bottom-up or top-down, it will confuse people.
>
> "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."
Right, will repost one.
Thanks!
next prev parent reply other threads:[~2017-03-08 9:08 UTC|newest]
Thread overview: 35+ 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 ` Baoquan He
[not found] ` <1488959258-4731-1-git-send-email-bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
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 7:47 ` Baoquan He
[not found] ` <1488959258-4731-2-git-send-email-bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-08 8:18 ` Dave Young
2017-03-08 8:18 ` Dave Young
[not found] ` <20170308081857.GB12600-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2017-03-08 8:35 ` Bhupesh Sharma
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:13 ` Baoquan He
2017-03-15 6:31 ` Baoquan He
2017-03-15 6:31 ` Baoquan He
2017-03-08 10:45 ` [PATCH v2 1/2] x86/efi/64: Clean up code comment about efi region Baoquan He
2017-03-08 10:45 ` Baoquan He
2017-03-08 8:18 ` [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment Dave Young
[not found] ` <20170308081812.GA12600-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2017-03-08 8:45 ` Baoquan He
2017-03-08 8:45 ` Baoquan He
2017-03-08 8:54 ` Borislav Petkov
2017-03-08 9:08 ` Baoquan He [this message]
2017-03-09 1:38 ` Dave Young
2017-03-08 9:00 ` Bhupesh Sharma
[not found] ` <CACi5LpOjxiiCEvdOHGxHj_c+G-W3HKHr8EgOURpZ-cb5XqQnNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-08 9:09 ` Baoquan He
2017-03-08 9:09 ` Baoquan He
2017-03-08 9:35 ` Borislav Petkov
2017-03-08 9:35 ` Borislav Petkov
[not found] ` <20170308093555.yrhygjxx4mu562lp-fF5Pk5pvG8Y@public.gmane.org>
2017-03-08 10:17 ` Baoquan He
2017-03-08 10:17 ` Baoquan He
2017-03-08 10:50 ` Borislav Petkov
[not found] ` <20170308105047.pggc6hai3gplsbg2-fF5Pk5pvG8Y@public.gmane.org>
2017-03-09 0:48 ` Dave Young
2017-03-09 0:48 ` Dave Young
2017-03-08 20:05 ` Bhupesh Sharma
2017-03-08 20:05 ` Bhupesh Sharma
2017-03-08 9:45 ` Baoquan He
2017-03-08 9:45 ` 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=20170308090833.GA6570@x1 \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.