[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3562b29-f035-47df-a23c-508a4ce85f95@intel.com>
Date: Tue, 16 Dec 2025 13:46:29 -0800
From: Reinette Chatre <reinette.chatre@...el.com>
To: Tony Luck <tony.luck@...el.com>, Fenghua Yu <fenghuay@...dia.com>, "Maciej
Wieczor-Retman" <maciej.wieczor-retman@...el.com>, Peter Newman
<peternewman@...gle.com>, James Morse <james.morse@....com>, Babu Moger
<babu.moger@....com>, Drew Fustini <dfustini@...libre.com>, Dave Martin
<Dave.Martin@....com>, Chen Yu <yu.c.chen@...el.com>
CC: <x86@...nel.org>, <linux-kernel@...r.kernel.org>,
<patches@...ts.linux.dev>
Subject: Re: [PATCH v16 24/32] x86/resctrl: Add energy/perf choices to rdt
boot option
Hi Tony,
On 12/10/25 3:14 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 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.
>
> Signed-off-by: Tony Luck <tony.luck@...el.com>
> ---
Reviewed-by: Reinette Chatre <reinette.chatre@...el.com>
Reinette
Powered by blists - more mailing lists