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 v2] x86,fs/resctrl: Add event group descriptions for Intel Diamond Rapids
Date: Wed, 30 Sep 2026 09:54:44 -0700 [thread overview]
Message-ID: <c6bcb782-7239-42a4-9689-81d063de40e9@intel.com> (raw)
In-Reply-To: <20260929171833.15883-1-tony.luck@intel.com>
Hi Tony,
On 9/29/26 10:18 AM, Tony Luck wrote:
...
> diff --git a/arch/x86/kernel/cpu/resctrl/intel_aet.c b/arch/x86/kernel/cpu/resctrl/intel_aet.c
> index c22c3cf5167d..3555b0aa33ce 100644
> --- a/arch/x86/kernel/cpu/resctrl/intel_aet.c
> +++ b/arch/x86/kernel/cpu/resctrl/intel_aet.c
...
> +/*
> + * Link: https://github.com/intel/Intel-PMT/blob/main/xml/DMR/OOBMSM/RMID-PERF/dmr_aggregator.xml
> + */
> +static struct event_group perf_0x1415910A = {
> + .pfname = "perf",
> + .guid = 0x1415910A,
> + .num_rmid = 256,
> + .mmio_size = XML_MMIO_SIZE(256, 4, 3),
> + .num_events = 4,
> + .evts = {
> + EVT(PMT_EVENT_UNHALTED_REF_CYCLES, 0, 0),
> + EVT(PMT_EVENT_UNHALTED_CORE_CYCLES, 1, 0),
> + EVT(PMT_EVENT_INST_RETIRED, 2, 0),
> + EVT(PMT_EVENT_PCNT, 3, 0),
> + }
> +};
> +
> static struct event_group *known_event_groups[] = {
> &energy_0x26696143,
> + &energy_0x47903099,
> &perf_0x26557651,
> + &perf_0x1415910A,
> };
>
I asked our internal AI to take a look and it pointed out that this is
the first GUID with a character hex digit. Having the GUID be uppercase
makes diagnostics a bit harder because all messages print GUIDs with
lowercase:
pr_warn("Bad package %u in guid 0x%x\n", tr->plat_info.package_id,
tr->guid);
pr_warn("MMIO space wrong size (%zu bytes) for guid 0x%x. Expected %zu bytes.\n",
tr->size, e->guid, e->mmio_size);
pr_info("No events enabled in %s %s:0x%x\n", r->name, e->pfname, e->guid);
pr_info("%s %s:0x%x monitoring detected\n", r->name, e->pfname, e->guid);
Going from log message to source code is thus not "grep friendly". This is
a valid point.
With event_group name and its guid value switched to lower case
| Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Reinette
prev parent reply other threads:[~2026-09-30 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 17:18 Tony Luck
2026-09-30 16:54 ` 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=c6bcb782-7239-42a4-9689-81d063de40e9@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®