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 v15 24/32] x86/resctrl: Add energy/perf choices to rdt boot option
Date: Tue, 9 Dec 2025 11:42:34 -0800 [thread overview]
Message-ID: <48d4dcc5-ef3d-4952-b70b-c0868a37f074@intel.com> (raw)
In-Reply-To: <20251204205404.12763-25-tony.luck@intel.com>
Hi Tony,
On 12/4/25 12:53 PM, Tony Luck wrote:
> Legacy resctrl features are enumerated by X86_FEATURE_* flags. These may be
> overridden by quirks to disable features in the case of errata. Users can
> use kernel command line options to either disable a feature, or to force
> enable a feature that was disabled by a quirk.
>
> A different approach is needed for hardware features that do not have an
> X86_FEATURE_* flag.
>
> Update the parse loop of the "rdt=" boot option with a call to intel_aet_option()
> to handles "perf" and "energy" options. Prefixing an option with "!" force
"to handles" -> "to handle"? ... although ... "Update the parse loop ... with a call to
intel_aet_option()" just describes what can be seen from the patch. Could this instead
describe on higher level what this code accomplishes? Consider, for example:
Update parsing of the "rdt=" boot parameter to call the telemetry driver
directly to handle new "perf" and "energy" options that controls activation
of telemetry monitoring of the named type. By itself a "perf" or "energy" option
controls the forced enabling or disabling (with ! prefix) of all event groups of
the named type. A ":guid" suffix allows for fine grain control per event group.
> disables a feature. A ":guid" suffix allows for fine grain control per-guid.
>
> Signed-off-by: Tony Luck <tony.luck@intel.com>
> ---
> .../admin-guide/kernel-parameters.txt | 7 +++-
> arch/x86/kernel/cpu/resctrl/internal.h | 2 ++
> arch/x86/kernel/cpu/resctrl/core.c | 2 ++
> arch/x86/kernel/cpu/resctrl/intel_aet.c | 34 +++++++++++++++++++
> 4 files changed, 44 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 2b465eab41a1..cc9d2800abeb 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -6217,9 +6217,14 @@
> rdt= [HW,X86,RDT]
> Turn on/off individual RDT features. List is:
> cmt, mbmtotal, mbmlocal, l3cat, l3cdp, l2cat, l2cdp,
> - mba, smba, bmec, abmc, sdciae.
> + mba, smba, bmec, abmc, sdciae, energy[:guid],
> + perf[:guid].
> E.g. to turn on cmt and turn off mba use:
> rdt=cmt,!mba
> + To turn off all energy telemetry monitoring and ensure that
> + perf telemetry monitoring associated with guid 0x12345
> + is enabled use:
> + rdt=!energy,perf:0x12345
>
> reboot= [KNL]
> Format (x86 or x86_64):
> diff --git a/arch/x86/kernel/cpu/resctrl/internal.h b/arch/x86/kernel/cpu/resctrl/internal.h
> index 3b228b241fb2..df09091f7c6c 100644
> --- a/arch/x86/kernel/cpu/resctrl/internal.h
> +++ b/arch/x86/kernel/cpu/resctrl/internal.h
> @@ -236,6 +236,7 @@ void __exit intel_aet_exit(void);
> int intel_aet_read_event(int domid, u32 rmid, void *arch_priv, u64 *val);
> void intel_aet_mon_domain_setup(int cpu, int id, struct rdt_resource *r,
> struct list_head *add_pos);
> +bool intel_aet_option(bool force_off, char *tok);
> #else
> static inline bool intel_aet_get_events(void) { return false; }
> static inline void __exit intel_aet_exit(void) { }
> @@ -246,6 +247,7 @@ static inline int intel_aet_read_event(int domid, u32 rmid, void *arch_priv, u64
>
> static inline void intel_aet_mon_domain_setup(int cpu, int id, struct rdt_resource *r,
> struct list_head *add_pos) { }
> +static inline bool intel_aet_option(bool force_off, char *tok) { return false; }
> #endif
>
> #endif /* _ASM_X86_RESCTRL_INTERNAL_H */
> diff --git a/arch/x86/kernel/cpu/resctrl/core.c b/arch/x86/kernel/cpu/resctrl/core.c
> index 283d653002a2..960974ffa866 100644
> --- a/arch/x86/kernel/cpu/resctrl/core.c
> +++ b/arch/x86/kernel/cpu/resctrl/core.c
> @@ -820,6 +820,8 @@ static int __init set_rdt_options(char *str)
> force_off = *tok == '!';
> if (force_off)
> tok++;
> + if (intel_aet_option(force_off, tok))
> + continue;
> for (o = rdt_options; o < &rdt_options[NUM_RDT_OPTIONS]; o++) {
> if (strcmp(tok, o->name) == 0) {
> if (force_off)
> diff --git a/arch/x86/kernel/cpu/resctrl/intel_aet.c b/arch/x86/kernel/cpu/resctrl/intel_aet.c
> index 8fcd72fca81f..fec4bb781f82 100644
> --- a/arch/x86/kernel/cpu/resctrl/intel_aet.c
> +++ b/arch/x86/kernel/cpu/resctrl/intel_aet.c
> @@ -59,6 +59,10 @@ struct pmt_event {
> * data for all telemetry regions of type @pfname.
> * Valid if the system supports the event group,
> * NULL otherwise.
> + * @force_off: True when "rdt" command line disables this @guid
> + * or architecture code disables this @guid.
"disables this @guid" is written twice. Even so, is the scope not event group? That is, would
it not be more accurate to say:
True when "rdt" command line or architecture disables this event group.
> + * @force_on: True when "rdt" command line overrides disable of
> + * this @guid.
"True when "rdt" command line overrides disable of this event group."?
> * @guid: Unique number per XML description file.
> * @mmio_size: Number of bytes of MMIO registers for this group.
> * @num_events: Number of events in this group.
> @@ -68,6 +72,7 @@ struct event_group {
> /* Data fields for additional structures to manage this group. */
> const char *pfname;
> struct pmt_feature_group *pfg;
> + bool force_off, force_on;
>
> /* Remaining fields initialized from XML file. */
> u32 guid;
> @@ -122,6 +127,32 @@ static struct event_group *known_event_groups[] = {
> _peg < &known_event_groups[ARRAY_SIZE(known_event_groups)]; \
> _peg++)
>
> +bool intel_aet_option(bool force_off, char *tok)
> +{
> + struct event_group **peg;
> + bool ret = false;
> + u32 guid = 0;
> + char *name;
> +
Could you please add a NULL check for tok?
> + name = strsep(&tok, ":");
> + if (tok && kstrtou32(tok, 16, &guid))
> + return false;
> +
> + for_each_event_group(peg) {
> + if (strcmp(name, (*peg)->pfname))
> + continue;
> + if (guid && (*peg)->guid != guid)
> + continue;
> + if (force_off)
> + (*peg)->force_off = true;
> + else
> + (*peg)->force_on = true;
> + ret = true;
> + }
> +
> + return ret;
> +}
> +
> /*
> * Clear the address field of regions that did not pass the checks in
> * skip_telem_region() so they will not be used by intel_aet_read_event().
> @@ -173,6 +204,9 @@ static bool enable_events(struct event_group *e, struct pmt_feature_group *p)
> struct rdt_resource *r = &rdt_resources_all[RDT_RESOURCE_PERF_PKG].r_resctrl;
> int skipped_events = 0;
>
> + if (e->force_off)
> + return false;
> +
> if (!group_has_usable_regions(e, p))
> return false;
>
Reinette
next prev parent reply other threads:[~2025-12-09 19:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 20:53 [PATCH v15 00/32] x86,fs/resctrl telemetry monitoring Tony Luck
2025-12-04 20:53 ` [PATCH v15 01/32] x86,fs/resctrl: Improve domain type checking Tony Luck
2025-12-04 20:53 ` [PATCH v15 02/32] x86/resctrl: Move L3 initialization into new helper function Tony Luck
2025-12-04 20:53 ` [PATCH v15 03/32] x86/resctrl: Refactor domain_remove_cpu_mon() ready for new domain types Tony Luck
2025-12-04 20:53 ` [PATCH v15 04/32] x86/resctrl: Clean up domain_remove_cpu_ctrl() Tony Luck
2025-12-04 20:53 ` [PATCH v15 05/32] x86,fs/resctrl: Refactor domain create/remove using struct rdt_domain_hdr Tony Luck
2025-12-04 20:53 ` [PATCH v15 06/32] fs/resctrl: Split L3 dependent parts out of __mon_event_count() Tony Luck
2025-12-04 20:53 ` [PATCH v15 07/32] x86,fs/resctrl: Use struct rdt_domain_hdr when reading counters Tony Luck
2025-12-09 19:38 ` Reinette Chatre
2025-12-04 20:53 ` [PATCH v15 08/32] x86,fs/resctrl: Rename struct rdt_mon_domain and rdt_hw_mon_domain Tony Luck
2025-12-09 19:38 ` Reinette Chatre
2025-12-04 20:53 ` [PATCH v15 09/32] x86,fs/resctrl: Rename some L3 specific functions Tony Luck
2025-12-04 20:53 ` [PATCH v15 10/32] fs/resctrl: Make event details accessible to functions when reading events Tony Luck
2025-12-04 20:53 ` [PATCH v15 11/32] x86,fs/resctrl: Handle events that can be read from any CPU Tony Luck
2025-12-09 19:39 ` Reinette Chatre
2025-12-09 20:37 ` Luck, Tony
2025-12-09 21:31 ` Reinette Chatre
2025-12-04 20:53 ` [PATCH v15 12/32] x86,fs/resctrl: Support binary fixed point event counters Tony Luck
2025-12-04 20:53 ` [PATCH v15 13/32] x86,fs/resctrl: Add an architectural hook called for each mount Tony Luck
2025-12-04 20:53 ` [PATCH v15 14/32] x86,fs/resctrl: Add and initialize a resource for package scope monitoring Tony Luck
2025-12-09 19:40 ` Reinette Chatre
2025-12-04 20:53 ` [PATCH v15 15/32] fs/resctrl: Emphasize that L3 monitoring resource is required for summing domains Tony Luck
2025-12-04 20:53 ` [PATCH v15 16/32] x86/resctrl: Discover hardware telemetry events Tony Luck
2025-12-09 19:41 ` Reinette Chatre
2025-12-04 20:53 ` [PATCH v15 17/32] x86,fs/resctrl: Fill in details of events for guid 0x26696143 and 0x26557651 Tony Luck
2025-12-09 19:41 ` Reinette Chatre
2025-12-04 20:53 ` [PATCH v15 18/32] x86,fs/resctrl: Add architectural event pointer Tony Luck
2025-12-04 20:53 ` [PATCH v15 19/32] x86/resctrl: Find and enable usable telemetry events Tony Luck
2025-12-09 19:41 ` Reinette Chatre
2025-12-04 20:53 ` [PATCH v15 20/32] x86/resctrl: Read " Tony Luck
2025-12-04 20:53 ` [PATCH v15 21/32] fs/resctrl: Refactor mkdir_mondata_subdir() Tony Luck
2025-12-04 20:53 ` [PATCH v15 22/32] fs/resctrl: Refactor rmdir_mondata_subdir_allrdtgrp() Tony Luck
2025-12-04 20:53 ` [PATCH v15 23/32] x86,fs/resctrl: Handle domain creation/deletion for RDT_RESOURCE_PERF_PKG Tony Luck
2025-12-04 20:53 ` [PATCH v15 24/32] x86/resctrl: Add energy/perf choices to rdt boot option Tony Luck
2025-12-09 19:42 ` Reinette Chatre [this message]
2025-12-04 20:53 ` [PATCH v15 25/32] x86/resctrl: Handle number of RMIDs supported by RDT_RESOURCE_PERF_PKG Tony Luck
2025-12-09 19:43 ` Reinette Chatre
2025-12-04 20:53 ` [PATCH v15 26/32] fs/resctrl: Move allocation/free of closid_num_dirty_rmid[] Tony Luck
2025-12-04 20:53 ` [PATCH v15 27/32] x86,fs/resctrl: Compute number of RMIDs as minimum across resources Tony Luck
2025-12-04 20:53 ` [PATCH v15 28/32] fs/resctrl: Move RMID initialization to first mount Tony Luck
2025-12-04 20:53 ` [PATCH v15 29/32] x86/resctrl: Enable RDT_RESOURCE_PERF_PKG Tony Luck
2025-12-04 20:54 ` [PATCH v15 30/32] fs/resctrl: Provide interface to create architecture specific debugfs area Tony Luck
2025-12-04 20:54 ` [PATCH v15 31/32] x86/resctrl: Add debugfs files to show telemetry aggregator status Tony Luck
2025-12-04 20:54 ` [PATCH v15 32/32] x86,fs/resctrl: Update documentation for telemetry events Tony Luck
2025-12-09 19:43 ` 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=48d4dcc5-ef3d-4952-b70b-c0868a37f074@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