From: Tony Luck <tony.luck@intel.com>
To: rafael@kernel.org
Cc: lenb@kernel.org,
Anil Keshavamurthy <anil.s.keshavamurthy@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, Tony Luck <tony.luck@intel.com>
Subject: [PATCH v4 0/4] Add interfaces for ACPI MRRM table
Date: Tue, 29 Apr 2025 13:24:07 -0700 [thread overview]
Message-ID: <20250429202412.380637-1-tony.luck@intel.com> (raw)
Memory used to be homogeneous. Then NUMA came along. Later different
types of memory (persistent memory, on-package high bandwidth memory,
CXL attached memory).
Each type of memory has its own performance characteristics, and users
will need to monitor and control access by type.
The MRRM solution is to tag physical address ranges with "region IDs"
so that platform firmware[1] can indicate the type of memory for each
range (with separate tags available for local vs. remote access to
each range). Note that these ranges can include addresses reserved
for future hotplugged memory.
The region IDs will be used to provide separate event counts for each
region for "perf" and for the "resctrl" file system to monitor and
control memory bandwidth in each region.
Users will need to know the address range(s) that are part of each
region. This patch series adds
/sys/firmware/acpi/memory_ranges/rangeX
directories to provide user space accessible enumeration.
-Tony
[1] MRRM definition allow for future expansion for the OS to assign
these region IDs.
Changes since version 3 here:
https://lore.kernel.org/all/20250410223207.257722-1-tony.luck@intel.com/
1) Rebase to v6.15-rc4
2) Removed ugly #ifdef in acpi_mrrm.c with better fix for CONFIG_NUMA=n
3) Moved stub for acpi_mrrm_max_mem_region() into #else !ACPI section
of <linux/acpi.h>
Tony Luck (4):
ACPICA: Define MRRM ACPI table
ACPI/MRRM: Minimal parse of ACPI MRRM table
ACPI/MRRM: Add /sys files to describe memory ranges
ACPI: Add documentation for exposing MRRM data
include/linux/acpi.h | 9 +
include/acpi/actbl1.h | 7 +
include/acpi/actbl2.h | 42 ++++
drivers/acpi/acpi_mrrm.c | 183 ++++++++++++++++++
Documentation/ABI/testing/sysfs-firmware-acpi | 21 ++
arch/x86/Kconfig | 1 +
drivers/acpi/Kconfig | 3 +
drivers/acpi/Makefile | 1 +
8 files changed, 267 insertions(+)
create mode 100644 drivers/acpi/acpi_mrrm.c
base-commit: b4432656b36e5cc1d50a1f2dc15357543add530e
--
2.48.1
next reply other threads:[~2025-04-29 20:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 20:24 Tony Luck [this message]
2025-04-29 20:24 ` [PATCH v4 1/4] ACPICA: Define MRRM ACPI table Tony Luck
2025-05-05 13:11 ` Rafael J. Wysocki
2025-05-05 17:12 ` Luck, Tony
2025-05-05 17:17 ` Rafael J. Wysocki
2025-04-29 20:24 ` [PATCH v4 2/4] ACPI/MRRM: Minimal parse of ACPI MRRM table Tony Luck
2025-04-29 20:24 ` [PATCH v4 3/4] ACPI/MRRM: Add /sys files to describe memory ranges Tony Luck
2025-05-05 6:23 ` Fenghua Yu
2025-05-05 16:28 ` Luck, Tony
2025-04-29 20:24 ` [PATCH v4 4/4] ACPI: Add documentation for exposing MRRM data Tony Luck
2025-05-05 6:34 ` Fenghua Yu
2025-05-05 16:45 ` Luck, Tony
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=20250429202412.380637-1-tony.luck@intel.com \
--to=tony.luck@intel.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--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