From: Robert Richter <rrichter@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-cxl@vger.kernel.org>, Robert Richter <rrichter@amd.com>
Subject: [PATCH v2 0/3] SRAT/CEDT fixes and updates
Date: Tue, 19 Mar 2024 13:00:22 +0100 [thread overview]
Message-ID: <20240319120026.2246389-1-rrichter@amd.com> (raw)
Some fixes and updates for SRAT/CEDT parsing code. Patches can be
applied individually and are independent.
First patch fixes a page fault during boot. It should be marked stable.
2nd patch adds diagnostic printouts for CEDT.
3rd patch removes architectural code no longer needed.
Robert Richter (3):
x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks()
ACPI/NUMA: Print CXL Early Discovery Table (CEDT)
ACPI/NUMA: Remove architecture dependent remainings
arch/x86/mm/numa.c | 4 +-
drivers/acpi/numa/srat.c | 178 +++++++++++++++++++++++++++++----------
include/linux/acpi.h | 5 --
3 files changed, 134 insertions(+), 53 deletions(-)
--
2.39.2
next reply other threads:[~2024-03-19 12:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 12:00 Robert Richter [this message]
2024-03-19 12:00 ` [PATCH v2 1/3] x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() Robert Richter
2024-03-19 20:15 ` Dan Williams
2024-03-21 8:09 ` Robert Richter
2024-03-20 17:46 ` Alison Schofield
2024-03-21 16:55 ` Robert Richter
2024-03-21 18:39 ` Alison Schofield
2024-03-21 22:17 ` Robert Richter
2024-03-19 12:00 ` [PATCH v2 2/3] ACPI/NUMA: Print CXL Early Discovery Table (CEDT) Robert Richter
2024-03-19 20:18 ` Dan Williams
2024-03-20 17:47 ` Alison Schofield
2024-03-19 12:00 ` [PATCH v2 3/3] ACPI/NUMA: Remove architecture dependent remainings Robert Richter
2024-03-19 20:44 ` Dan Williams
2024-03-22 2:12 ` kernel test robot
2024-03-28 16:49 ` Robert Richter
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=20240319120026.2246389-1-rrichter@amd.com \
--to=rrichter@amd.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).