From: Steve Wahl <steve.wahl@hpe.com>
To: 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>,
Steve Wahl <steve.wahl@hpe.com>,
Jordan Borgner <mail@jordan-borgner.de>,
Feng Tang <feng.tang@intel.com>,
linux-kernel@vger.kernel.org,
Zhenzhong Duan <zhenzhong.duan@oracle.com>,
Dave Hansen <dave.hansen@intel.com>
Cc: Baoquan He <bhe@redhat.com>,
russ.anderson@hpe.com, dimitri.sivanich@hpe.com,
mike.travis@hpe.com
Subject: Re: [PATCH v3 0/2] x86/boot/64: Avoid mapping reserved ranges in early page tables.
Date: Thu, 10 Oct 2019 14:27:42 -0500 [thread overview]
Message-ID: <20191010192742.GX2113@swahl-linux> (raw)
In-Reply-To: <cover.1569358538.git.steve.wahl@hpe.com>
It's been a while on this patch set; two weeks ago Kirill added acks,
no movement since. Is there anything I need to be doing on my part to
move this forward?
Thanks!
--> Steve Wahl
On Tue, Sep 24, 2019 at 04:03:22PM -0500, Steve Wahl wrote:
> This patch set narrows the valid space addressed by the page table
> level2_kernel_pgt to only contain ranges checked against the "usable
> RAM" list provided by the BIOS.
>
> Prior to this, some larger than needed mappings were occasionally
> crossing over into spaces marked reserved, allowing the processor to
> access these reserved spaces, which were caught by the hardware and
> caused BIOS to halt on our platform (UV).
>
> Changes since v1:
>
> * Cover letter added because there's now two patches.
>
> * Patch 1: Added comment and re-worked changelog text.
>
> * Patch 2: New change requested by Dave Hansen to handle the case that
> the mapping of the last PMD page for the kernel image could cross a
> reserved region boundary.
>
> Changes since v2:
>
> * Patch 1: Added further inline comments.
> * Patch 2: None.
>
> Steve Wahl (2):
> x86/boot/64: Make level2_kernel_pgt pages invalid outside kernel area.
> x86/boot/64: round memory hole size up to next PMD page.
>
> arch/x86/boot/compressed/misc.c | 25 +++++++++++++++++++------
> arch/x86/kernel/head64.c | 22 ++++++++++++++++++++--
> 2 files changed, 39 insertions(+), 8 deletions(-)
>
> --
> 2.21.0
>
>
> --
> Steve Wahl, Hewlett Packard Enterprise
--
Steve Wahl, Hewlett Packard Enterprise
prev parent reply other threads:[~2019-10-10 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 21:03 [PATCH v3 0/2] x86/boot/64: Avoid mapping reserved ranges in early page tables Steve Wahl
2019-09-24 21:03 ` [PATCH v3 1/2] x86/boot/64: Make level2_kernel_pgt pages invalid outside kernel area Steve Wahl
2019-09-26 10:23 ` Kirill A. Shutemov
2019-10-11 16:02 ` Dave Hansen
2019-10-11 18:27 ` [tip: x86/urgent] " tip-bot2 for Steve Wahl
2019-10-11 18:27 ` tip-bot2 for Steve Wahl
2019-09-24 21:04 ` [PATCH v3 2/2] x86/boot/64: round memory hole size up to next PMD page Steve Wahl
2019-09-26 10:23 ` Kirill A. Shutemov
2019-10-11 18:27 ` [tip: x86/urgent] x86/boot/64: Round " tip-bot2 for Steve Wahl
2019-10-11 18:27 ` tip-bot2 for Steve Wahl
2019-10-10 19:27 ` 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=20191010192742.GX2113@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=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