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 v16 19/32] x86/resctrl: Find and enable usable telemetry events
Date: Tue, 16 Dec 2025 13:47:31 -0800 [thread overview]
Message-ID: <cfd4b8aa-61d2-4535-88f5-c7370a3cb750@intel.com> (raw)
In-Reply-To: <20251210231413.59102-20-tony.luck@intel.com>
Hi Tony,
On 12/10/25 3:13 PM, Tony Luck wrote:
> Every event group has a private copy of the data of all telemetry event
> aggregators (aka "telemetry regions") tracking its feature type. Included
> may be regions that have the same feature type but tracking different guid
> from the event group's.
>
> Traverse the event group's telemetry region data and mark all regions that
> are not usable by the event group as unusable by clearing those regions'
> MMIO addresses. A region is considered unusable if:
> 1) guid does not match the guid of the event group.
> 2) Package ID is invalid.
> 3) The enumerated size of the MMIO region does not match the expected
> value from the XML description file.
>
> Hereafter any telemetry region with an MMIO address is considered valid for
> the event group it is associated with.
>
> Enable all the event group's events as long as there is at least one usable
> region from where data for its events can be read. Enabling of events
> can fail. Each event group is independent of other event groups. So even
> if no events can be enabled from one event group, keep running to enable
> other event groups.
Above describes how event groups are independent while I see the question needing
to be answered here as "Why enable an event group if one or more of its events
cannot be enabled?"
How about something like:
Enabling of an event can fail if the same event has already been enabled as
part of another event group. It should never happen that the same event is
described by different guid supported by the same system so just WARN (via
resctrl_enable_mon_event()) and skip the event."
Can the "should" be replaced with a specific reason why this can never happen?
>
> Note that it is architecturally possible that some telemetry events are
> only supported by a subset of the packages in the system. It is not expected
> that systems will ever do this. If they do the user will see event files in
> resctrl that always return "Unavailable".
>
> Signed-off-by: Tony Luck <tony.luck@intel.com>
| Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Reinette
next prev parent reply other threads:[~2025-12-16 21:47 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 23:13 [PATCH v16 00/32] x86,fs/resctrl telemetry monitoring Tony Luck
2025-12-10 23:13 ` [PATCH v16 01/32] x86,fs/resctrl: Improve domain type checking Tony Luck
2025-12-10 23:13 ` [PATCH v16 02/32] x86/resctrl: Move L3 initialization into new helper function Tony Luck
2025-12-10 23:13 ` [PATCH v16 03/32] x86/resctrl: Refactor domain_remove_cpu_mon() ready for new domain types Tony Luck
2025-12-10 23:13 ` [PATCH v16 04/32] x86/resctrl: Clean up domain_remove_cpu_ctrl() Tony Luck
2025-12-10 23:13 ` [PATCH v16 05/32] x86,fs/resctrl: Refactor domain create/remove using struct rdt_domain_hdr Tony Luck
2025-12-10 23:13 ` [PATCH v16 06/32] fs/resctrl: Split L3 dependent parts out of __mon_event_count() Tony Luck
2025-12-10 23:13 ` [PATCH v16 07/32] x86,fs/resctrl: Use struct rdt_domain_hdr when reading counters Tony Luck
2025-12-10 23:13 ` [PATCH v16 08/32] x86,fs/resctrl: Rename struct rdt_mon_domain and rdt_hw_mon_domain Tony Luck
2025-12-10 23:13 ` [PATCH v16 09/32] x86,fs/resctrl: Rename some L3 specific functions Tony Luck
2025-12-10 23:13 ` [PATCH v16 10/32] fs/resctrl: Make event details accessible to functions when reading events Tony Luck
2025-12-10 23:13 ` [PATCH v16 11/32] x86,fs/resctrl: Handle events that can be read from any CPU Tony Luck
2025-12-16 21:46 ` Reinette Chatre
2025-12-10 23:13 ` [PATCH v16 12/32] x86,fs/resctrl: Support binary fixed point event counters Tony Luck
2025-12-10 23:13 ` [PATCH v16 13/32] x86,fs/resctrl: Add an architectural hook called for each mount Tony Luck
2025-12-10 23:13 ` [PATCH v16 14/32] x86,fs/resctrl: Add and initialize a resource for package scope monitoring Tony Luck
2025-12-10 23:13 ` [PATCH v16 15/32] fs/resctrl: Emphasize that L3 monitoring resource is required for summing domains Tony Luck
2025-12-10 23:13 ` [PATCH v16 16/32] x86/resctrl: Discover hardware telemetry events Tony Luck
2025-12-10 23:13 ` [PATCH v16 17/32] x86,fs/resctrl: Fill in details of events for guid 0x26696143 and 0x26557651 Tony Luck
2025-12-10 23:13 ` [PATCH v16 18/32] x86,fs/resctrl: Add architectural event pointer Tony Luck
2025-12-10 23:13 ` [PATCH v16 19/32] x86/resctrl: Find and enable usable telemetry events Tony Luck
2025-12-16 21:47 ` Reinette Chatre [this message]
2025-12-10 23:13 ` [PATCH v16 20/32] x86/resctrl: Read " Tony Luck
2025-12-10 23:14 ` [PATCH v16 21/32] fs/resctrl: Refactor mkdir_mondata_subdir() Tony Luck
2025-12-10 23:14 ` [PATCH v16 22/32] fs/resctrl: Refactor rmdir_mondata_subdir_allrdtgrp() Tony Luck
2025-12-10 23:14 ` [PATCH v16 23/32] x86,fs/resctrl: Handle domain creation/deletion for RDT_RESOURCE_PERF_PKG Tony Luck
2025-12-10 23:14 ` [PATCH v16 24/32] x86/resctrl: Add energy/perf choices to rdt boot option Tony Luck
2025-12-16 21:46 ` Reinette Chatre
2025-12-10 23:14 ` [PATCH v16 25/32] x86/resctrl: Handle number of RMIDs supported by RDT_RESOURCE_PERF_PKG Tony Luck
2025-12-16 21:46 ` Reinette Chatre
2025-12-10 23:14 ` [PATCH v16 26/32] fs/resctrl: Move allocation/free of closid_num_dirty_rmid[] Tony Luck
2025-12-10 23:14 ` [PATCH v16 27/32] x86,fs/resctrl: Compute number of RMIDs as minimum across resources Tony Luck
2025-12-10 23:14 ` [PATCH v16 28/32] fs/resctrl: Move RMID initialization to first mount Tony Luck
2025-12-10 23:14 ` [PATCH v16 29/32] x86/resctrl: Enable RDT_RESOURCE_PERF_PKG Tony Luck
2025-12-10 23:14 ` [PATCH v16 30/32] fs/resctrl: Provide interface to create architecture specific debugfs area Tony Luck
2025-12-10 23:14 ` [PATCH v16 31/32] x86/resctrl: Add debugfs files to show telemetry aggregator status Tony Luck
2025-12-10 23:14 ` [PATCH v16 32/32] x86,fs/resctrl: Update documentation for telemetry events Tony Luck
2025-12-16 21:48 ` Reinette Chatre
2025-12-16 21:46 ` [PATCH v16 00/32] x86,fs/resctrl telemetry monitoring Reinette Chatre
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=cfd4b8aa-61d2-4535-88f5-c7370a3cb750@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®