From: Namhyung Kim <namhyung@kernel.org>
To: "Falcon, Thomas" <thomas.falcon@intel.com>
Cc: "james.clark@linaro.org" <james.clark@linaro.org>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"acme@kernel.org" <acme@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"dapeng1.mi@linux.intel.com" <dapeng1.mi@linux.intel.com>,
"Rogers, Ian" <irogers@google.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>
Subject: Re: [PATCH v2 5/6] perf header: Support memory ranges
Date: Fri, 31 Jul 2026 14:38:54 -0700 [thread overview]
Message-ID: <am0V7muVNcfsLQYr@google.com> (raw)
In-Reply-To: <329ae3d6ad1419fc356995badc5f7de5be422ba3.camel@intel.com>
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
next prev parent reply other threads:[~2026-07-31 21:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 0:43 [PATCH v2 0/6] perf: Add support for memory region/range reporting Thomas Falcon
2026-07-14 0:43 ` [PATCH v2 1/6] perf mem: Fix size tracking for mem_lvl's in perf_script__meminfo_scnprintf() Thomas Falcon
2026-07-14 0:51 ` sashiko-bot
2026-07-27 17:06 ` Falcon, Thomas
2026-07-15 6:59 ` Mi, Dapeng
2026-07-14 0:43 ` [PATCH v2 2/6] perf mem: Add support for printing PERF_MEM_LVLNUM_L0 Thomas Falcon
2026-07-15 7:11 ` Mi, Dapeng
2026-07-28 17:13 ` Namhyung Kim
2026-07-30 5:46 ` Mi, Dapeng
2026-07-31 21:37 ` Namhyung Kim
2026-07-14 0:43 ` [PATCH v2 3/6] perf tools: Show memory region in perf-c2c subcommand Thomas Falcon
2026-07-14 0:56 ` sashiko-bot
2026-07-27 16:37 ` Falcon, Thomas
2026-07-28 17:17 ` Namhyung Kim
2026-07-30 5:50 ` Mi, Dapeng
2026-07-14 0:43 ` [PATCH v2 4/6] perf tools: Show memory region in perf-script subcommand Thomas Falcon
2026-07-14 0:59 ` sashiko-bot
2026-07-28 17:18 ` Namhyung Kim
2026-07-30 5:50 ` Mi, Dapeng
2026-07-14 0:43 ` [PATCH v2 5/6] perf header: Support memory ranges Thomas Falcon
2026-07-28 17:33 ` Namhyung Kim
2026-07-28 21:33 ` Falcon, Thomas
2026-07-31 21:38 ` Namhyung Kim [this message]
2026-07-14 0:43 ` [PATCH v2 6/6] perf c2c: print memory region data with stdio output Thomas Falcon
2026-07-14 0:57 ` sashiko-bot
2026-07-27 17:05 ` Falcon, Thomas
2026-07-28 17:34 ` Namhyung Kim
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=am0V7muVNcfsLQYr@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=thomas.falcon@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