From: Steve Wahl <steve.wahl@hpe.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Steve Wahl <steve.wahl@hpe.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Juergen Gross <jgross@suse.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Brijesh Singh <brijesh.singh@amd.com>,
Jordan Borgner <mail@jordan-borgner.de>,
Feng Tang <feng.tang@intel.com>,
linux-kernel@vger.kernel.org, Chao Fan <fanc.fnst@cn.fujitsu.com>,
Zhenzhong Duan <zhenzhong.duan@oracle.com>,
Baoquan He <bhe@redhat.com>,
russ.anderson@hpe.com, dimitri.sivanich@hpe.com,
mike.travis@hpe.com
Subject: Re: [PATCH v2 2/2] x86/boot/64: round memory hole size up to next PMD page.
Date: Tue, 24 Sep 2019 14:48:19 -0500 [thread overview]
Message-ID: <20190924194819.GB8138@swahl-linux> (raw)
In-Reply-To: <edd60d59-fdfc-2383-6cc8-e084e86e7a37@intel.com>
On Mon, Sep 23, 2019 at 02:20:35PM -0700, Dave Hansen wrote:
> On 9/23/19 11:15 AM, Steve Wahl wrote:
> > The kernel image map is created using PMD pages, which can include
> > some extra space beyond what's actually needed. Round the size of the
> > memory hole we search for up to the next PMD boundary, to be certain
> > all of the space to be mapped is usable RAM and includes no reserved
> > areas.
>
> This looks good. It also fully closes any possibility that anyone's
> future hardware will hit issues like this as long as they mark the
> memory reserved, right?
I believe that is true. Thanks!
> Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com>
--> Steve Wahl
--
Steve Wahl, Hewlett Packard Enterprise
prev parent reply other threads:[~2019-09-24 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 18:14 [PATCH v2 0/2] x86/boot/64: Avoid mapping reserved ranges in early page tables Steve Wahl
2019-09-23 18:15 ` [PATCH v2 1/2] x86/boot/64: Make level2_kernel_pgt pages invalid outside kernel area Steve Wahl
2019-09-23 18:49 ` hpa
2019-09-24 16:32 ` Steve Wahl
2019-09-23 21:19 ` Dave Hansen
2019-09-24 20:04 ` Steve Wahl
2019-09-24 20:15 ` Dave Hansen
2019-09-23 18:15 ` [PATCH v2 2/2] x86/boot/64: round memory hole size up to next PMD page Steve Wahl
2019-09-23 21:20 ` Dave Hansen
2019-09-24 19:48 ` Steve Wahl [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=20190924194819.GB8138@swahl-linux \
--to=steve.wahl@hpe.com \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dave.hansen@intel.com \
--cc=dimitri.sivanich@hpe.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=feng.tang@intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@jordan-borgner.de \
--cc=mike.travis@hpe.com \
--cc=mingo@redhat.com \
--cc=russ.anderson@hpe.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zhenzhong.duan@oracle.com \
/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