From: "Luck, Tony" <tony.luck@intel.com>
To: Fenghua Yu <fenghuay@nvidia.com>
Cc: rafael@kernel.org, lenb@kernel.org,
Anil Keshavamurthy <anil.s.keshavamurthy@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH v4 4/4] ACPI: Add documentation for exposing MRRM data
Date: Mon, 5 May 2025 09:45:26 -0700 [thread overview]
Message-ID: <aBjrJvs-wuViTOSI@agluck-desk3> (raw)
In-Reply-To: <a5a6e279-82ec-4282-9cf2-6ec4a77a38f1@nvidia.com>
On Sun, May 04, 2025 at 11:34:51PM -0700, Fenghua Yu wrote:
> Hi, Tony,
>
> On 4/29/25 13:24, Tony Luck wrote:
> > Initial implementation provides enumeration of the address ranges
> > NUMA node numbers, and BIOS assigned region IDs for each range.
> >
> > Signed-off-by: Tony Luck <tony.luck@intel.com>
> > ---
> > Documentation/ABI/testing/sysfs-firmware-acpi | 21 +++++++++++++++++++
> > 1 file changed, 21 insertions(+)
> >
> > diff --git a/Documentation/ABI/testing/sysfs-firmware-acpi b/Documentation/ABI/testing/sysfs-firmware-acpi
> > index 5249ad5a96d9..fffba38f9ce1 100644
> > --- a/Documentation/ABI/testing/sysfs-firmware-acpi
> > +++ b/Documentation/ABI/testing/sysfs-firmware-acpi
> > @@ -248,3 +248,24 @@ 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.
>
> Is there a need to explain what's "X" here? The "X" is not a number directly
> reported by MRRM, right?
>
> Maybe something like "range ID is enumerated from MRRM starting from 0."?
I'm not sure about this one. "X" in the ABI documentation files is a
standard notation for "there are several of these with a number for
each". When the number does refer to some physical object, then there
may be a need to describe it. But if it is simply a counter to give a
separate name for each one of some repeating thing ... then I don't
think it helps to add additional explanation.
>
> > +
> > + base: Starting system physical address.
> > +
> > + length: Length of this range in bytes.
> > +
> > + node: NUMA node that this range belongs to. Negative numbers
> > + indicate that the node number could not be determined (e.g
> > + for an address range that is reserved for future hot add of
> > + memory).
> > +
> > + 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.
>
> Thanks.
>
> -Fenghua
-Tony
prev parent reply other threads:[~2025-05-05 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 20:24 [PATCH v4 0/4] Add interfaces for ACPI MRRM table Tony Luck
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 [this message]
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=aBjrJvs-wuViTOSI@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=fenghuay@nvidia.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