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 v7 0/4] SRAT/CEDT fixes and updates
Date: Thu, 2 May 2024 15:10:08 +0200 [thread overview]
Message-ID: <20240502131012.2385725-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 (fix as suggested by Dan).
Patches 2 to 4 remove architectural code no longer needed.
Changelog:
v7:
* added Reviewed-by tags
* dropped printout patches (#5 to #7)
v6:
* rebased onto cxl/fixes
* fixed 0day build errors in patch #1:
https://github.com/intel-lab-lkp/linux/commits/Robert-Richter/x86-numa-Fix-SRAT-lookup-of-CFMWS-ranges-with-numa_fill_memblks/20240429-205337
v5:
* dropped: "x86/numa: Fix SRAT lookup of CFMWS ranges with
numa_fill_memblks()"
* added: "ACPI/NUMA: Return memblk modification state from
numa_fill_memblks()"
* conditionally print CEDT extended memblks
v4:
* updated SOB chains and desription
* added patch "x86/numa: Remove numa_fill_memblks() from sparsemem.h
using __weak"
* Reordered patches to move CEDT table printout as an option at the
end
* split print table patch and added: "ACPI/NUMA: Add log messages for
memory ranges found in CEDT"
v3:
* Rebased onto v6.9-rc1
* Fixing x86 build error in sparsemem.h [Dan/Alison]
* Added CEDT node info [Alison]
* Use pr_debug() for table output [Dan]
* Refactoring split in 3 patches [Dan]
* Fixed performance regression introduced [kbot]
* Fixed checkpatch issues [Dan]
Robert Richter (4):
x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks()
ACPI/NUMA: Remove architecture dependent remainings
ACPI/NUMA: Squash acpi_numa_slit_init() into acpi_parse_slit()
ACPI/NUMA: Squash acpi_numa_memory_affinity_init() into
acpi_parse_memory_affinity()
arch/x86/include/asm/sparsemem.h | 2 -
arch/x86/mm/numa.c | 4 +-
drivers/acpi/numa/srat.c | 82 +++++++++++++-------------------
include/linux/acpi.h | 5 --
include/linux/numa.h | 7 +--
5 files changed, 35 insertions(+), 65 deletions(-)
base-commit: 5d211c7090590033581175d6405ae40917ca3a06
--
2.39.2
next reply other threads:[~2024-05-02 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 13:10 Robert Richter [this message]
2024-05-02 13:10 ` [PATCH v7 1/4] x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() Robert Richter
2024-05-03 19:46 ` Borislav Petkov
2024-05-02 13:10 ` [PATCH v7 2/4] ACPI/NUMA: Remove architecture dependent remainings Robert Richter
2024-05-02 13:10 ` [PATCH v7 3/4] ACPI/NUMA: Squash acpi_numa_slit_init() into acpi_parse_slit() Robert Richter
2024-05-02 13:10 ` [PATCH v7 4/4] ACPI/NUMA: Squash acpi_numa_memory_affinity_init() into acpi_parse_memory_affinity() Robert Richter
2024-05-07 11:48 ` [PATCH v7 0/4] SRAT/CEDT fixes and updates Rafael J. Wysocki
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=20240502131012.2385725-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).