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 3/4] ACPI: Add documentation for exposing MRRM data
Date: Thu, 27 Feb 2025 14:48:27 -0800 [thread overview]
Message-ID: <20250227224828.306537-4-tony.luck@intel.com> (raw)
In-Reply-To: <20250227224828.306537-1-tony.luck@intel.com>
Initial implementation provides enumeration of the address ranges
and BIOS assigned region IDs for each range.
Signed-off-by: Tony Luck <tony.luck@intel.com>
---
Documentation/ABI/testing/sysfs-firmware-acpi | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-firmware-acpi b/Documentation/ABI/testing/sysfs-firmware-acpi
index 5249ad5a96d9..a3369cf95546 100644
--- a/Documentation/ABI/testing/sysfs-firmware-acpi
+++ b/Documentation/ABI/testing/sysfs-firmware-acpi
@@ -248,3 +248,19 @@ Description:
# cat ff_pwr_btn
7 enabled
+What: /sys/firmware/acpi/memory_ranges/rangeX
+Date: February 2025
+Contact: Tony Luck <tony.luck@intel.com>
+Description:
+ On systems with the ACPI MRRM table reports the
+ parameters for each range.
+
+ base: Starting system physical address.
+
+ length: Length of this range in bytes.
+
+ local_region_id: ID associated with access by agents
+ local to this range of addresses.
+
+ remote_region_id: ID associated with access by agents
+ non-local to this range of addresses.
--
2.48.1
next prev parent 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 [PATCH v2 0/4] Add interfaces for ACPI MRRM table Tony Luck
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 ` Tony Luck [this message]
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-4-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