From: Reinette Chatre <reinette.chatre@intel.com>
To: Tony Luck <tony.luck@intel.com>, Fenghua Yu <fenghuay@nvidia.com>,
"Maciej Wieczor-Retman" <maciej.wieczor-retman@intel.com>,
Peter Newman <peternewman@google.com>,
James Morse <james.morse@arm.com>,
Babu Moger <babu.moger@amd.com>,
Drew Fustini <dfustini@baylibre.com>,
Dave Martin <Dave.Martin@arm.com>, Chen Yu <yu.c.chen@intel.com>
Cc: <x86@kernel.org>, <linux-kernel@vger.kernel.org>,
<patches@lists.linux.dev>
Subject: Re: [PATCH] x86,fs/resctrl: Add event_group information for Intel Diamond Rapids
Date: Mon, 28 Sep 2026 17:09:18 -0700 [thread overview]
Message-ID: <9d7fea8b-c727-4acf-babe-4c8665af2062@intel.com> (raw)
In-Reply-To: <20260921213226.14997-1-tony.luck@intel.com>
Hi Tony,
On 9/21/26 2:32 PM, Tony Luck wrote:
> Intel published XML descriptions for the Application Energy Telemetry
> events on Diamond Rapids here: https://github.com/intel/Intel-PMT.
See "Link:" in Documentation/process/maintainer-tip.rst
>
> Add event_group structures for both new GUIDs.
"Add event_group structures" describes actual code and is clear from the patch.
What does "both" refer to?
>
> There are two new "perf" events. Add them to the resctrl file system.
Here it becomes confusing since patch adds two event groups
as well as two events.
Below is an attempt at a changelog that follows tip requirements. Could
you please consider this as a draft and build on it to use accurate
terminology and be accurate for this patch?
x86,fs/resctrl: Add event group descriptions for Intel Diamond Rapids
Intel Diamond Rapids exposes Application Energy Telemetry through two
new PMT aggregator GUIDs: one covering the "energy" feature, and one
covering the "perf" feature, both documented in the Intel-PMT XML
repository [1].
The "perf" aggregator references two events not previously enumerated
by resctrl: retired instructions (INST_RETIRED), and a count of
unhalted core clock cycles perceived by hardware as contributing to
instruction execution (PCNT).
Add definitions for both aggregators, and add the two new events to
the resctrl filesystem so they can be exposed to user space.
Signed-off-by: Tony Luck <tony.luck@intel.com>
Link: https://github.com/intel/Intel-PMT # [1]
>
> Signed-off-by: Tony Luck <tony.luck@intel.com>
> ---
patch looks good.
Reinette
prev parent reply other threads:[~2026-09-29 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 21:32 Tony Luck
2026-09-29 0:09 ` Reinette Chatre [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=9d7fea8b-c727-4acf-babe-4c8665af2062@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=dfustini@baylibre.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=patches@lists.linux.dev \
--cc=peternewman@google.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yu.c.chen@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
all inboxes | Powered by JetHome®