public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Luck <tony.luck@intel.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@lists.linux.dev, Tony Luck <tony.luck@intel.com>
Subject: [PATCH v2 0/4] Add interfaces for ACPI MRRM table
Date: Thu, 27 Feb 2025 14:48:24 -0800	[thread overview]
Message-ID: <20250227224828.306537-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 v1 posted at:
  https://lore.kernel.org/all/20250210211223.6139-1-tony.luck@intel.com/

1) Target /sys directory for the files moved from
  /sys/devices/system/memory to /sys/firmware/acpi/memory.

While the old target had a useful sounding name, it is really all about
hotplug memory while this enumeration is about different types of memory
with hotplug being a non-issue as memory ranges can describe addresses
that are reserved for future addition of different types of memory.

2) The ACPICA changes in patch one have been committed to the acpica
git repository and will make their way into Linux for the next ACPICA
release. Patch included here for convenience.

3) I included a "testing" patch that provides a fake MRRM table so
that anyone can compile and run this series to check things out.

Tony Luck (4):
  ACPICA: Define MRRM ACPI table
  ACPI/MRRM: Create /sys/firmware/acpi/memory_ranges/rangeX ABI
  ACPI: Add documentation for exposing MRRM data
  acpi_mrrm: fake for testing, do not apply!

 include/linux/acpi.h                          |   6 +
 include/acpi/actbl1.h                         |   7 +
 include/acpi/actbl2.h                         |  42 ++++
 drivers/acpi/acpi_mrrm.c                      | 185 ++++++++++++++++++
 Documentation/ABI/testing/sysfs-firmware-acpi |  16 ++
 arch/x86/Kconfig                              |   1 +
 drivers/acpi/Kconfig                          |   3 +
 drivers/acpi/Makefile                         |   1 +
 8 files changed, 261 insertions(+)
 create mode 100644 drivers/acpi/acpi_mrrm.c


base-commit: d082ecbc71e9e0bf49883ee4afd435a77a5101b6
-- 
2.48.1


             reply	other threads:[~2025-02-27 22:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 22:48 Tony Luck [this message]
2025-02-27 22:48 ` [PATCH v2 1/4] ACPICA: Define MRRM ACPI table Tony Luck
2025-02-27 22:48 ` [PATCH v2 2/4] ACPI/MRRM: Create /sys/firmware/acpi/memory_ranges/rangeX ABI Tony Luck
2025-02-27 22:48 ` [PATCH v2 3/4] ACPI: Add documentation for exposing MRRM data Tony Luck
2025-02-27 22:48 ` [PATCH v2 4/4] acpi_mrrm: fake for testing, do not apply! Tony Luck

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=20250227224828.306537-1-tony.luck@intel.com \
    --to=tony.luck@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.j.wysocki@intel.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