Re: [PATCH v2 5/6] perf header: Support memory ranges

From: Namhyung Kim

Date: Fri Jul 31 2026 - 17:44:19 EST


On Tue, Jul 28, 2026 at 09:33:13PM +0000, Falcon, Thomas wrote:
> On Tue, 2026-07-28 at 10:33 -0700, Namhyung Kim wrote:
> > On Mon, Jul 13, 2026 at 07:43:58PM -0500, Thomas Falcon wrote:
> > > Memory ranges were created to track different types of memory,
> > > such as persistent, high bandwidth, or CXL-attached, that may
> > > be present on a system for performance monitoring and resource
> > > control purposes.
> > >
> > > Memory range data are parsed from the ACPI MRRM table and exposed
> > > to userspace tools via sysfs [1]. Memory range data is read from:
> > >
> > > /sys/firmware/acpi/memory_ranges/rangeX
> > >
> > > With the following attributes:
> > >
> > > u64 base;
> > > u64 length;
> > > int node;
> > > u8  local_region_id;
> > > u8  remote_region_id;
> > >
> > > Read memory range data from sysfs if present and save it in
> > > the header of the perf data file under a new feature bit,
> > > HEADER_MEMORY_RANGES (35). Memory range data can be viewed with the
> > > --header or --header-only options of perf-report and perf-script.
> >
> > Can you please add an example output here?
>
> Hi, thanks for reviewing. To be honest, I have not been able to get
> access to supported hardware yet so the only example I can provide
> would look like this (on a non-capable system)
>
> # memory ranges (nr 0):
>
> I will look into getting access to one and, in the meantime, make the
> other changes you requested.

Thanks, it'd be nice to see a real output. :)

Namhyung