From: Ross Philipson <ross.philipson@oracle.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: ross.philipson@oracle.com, daniel.kiper@oracle.com,
dpsmith@apertussolutions.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, hpa@zytor.com,
luto@amacapital.net, kanth.ghatraju@oracle.com,
trenchboot-devel@googlegroups.com
Subject: [PATCH 0/2] x86/boot: Fix setup_indirect support
Date: Thu, 27 Jan 2022 12:04:14 -0500 [thread overview]
Message-ID: <1643303056-22272-1-git-send-email-ross.philipson@oracle.com> (raw)
The setup_indirect support for x86 setup_data was added in November
of 2019. Several issues were found in the implementation and these
two patches were created to address those issues.
These patches were originally posted as part of the larger Trenchboot
patch set but are now being posted separately since they have been
reviewed and can be merged independently of the Trenchboot work.
Ross Philipson (2):
x86/boot: Fix memremap of setup_indirect structures
x86/boot: Add setup_indirect support in early_memremap_is_setup_data
arch/x86/kernel/e820.c | 31 ++++++++++++++++---------
arch/x86/kernel/kdebugfs.c | 32 +++++++++++++++++++-------
arch/x86/kernel/ksysfs.c | 56 ++++++++++++++++++++++++++++++++++++----------
arch/x86/kernel/setup.c | 23 +++++++++++++------
arch/x86/mm/ioremap.c | 34 +++++++++++++++++++++++-----
5 files changed, 132 insertions(+), 44 deletions(-)
--
1.8.3.1
next reply other threads:[~2022-01-27 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 17:04 Ross Philipson [this message]
2022-01-27 17:04 ` [PATCH 1/2] x86/boot: Fix memremap of setup_indirect structures Ross Philipson
2022-02-11 17:24 ` Borislav Petkov
2022-02-15 11:34 ` Ross Philipson
2022-02-15 18:37 ` Borislav Petkov
2022-02-22 21:01 ` Ross Philipson
2022-02-24 13:42 ` Borislav Petkov
2022-02-24 15:13 ` Ross Philipson
2022-01-27 17:04 ` [PATCH 2/2] x86/boot: Add setup_indirect support in early_memremap_is_setup_data Ross Philipson
2022-02-11 18:41 ` Borislav Petkov
2022-02-15 11:36 ` Ross Philipson
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=1643303056-22272-1-git-send-email-ross.philipson@oracle.com \
--to=ross.philipson@oracle.com \
--cc=bp@alien8.de \
--cc=daniel.kiper@oracle.com \
--cc=dpsmith@apertussolutions.com \
--cc=hpa@zytor.com \
--cc=kanth.ghatraju@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=trenchboot-devel@googlegroups.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®