[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <40858873-6cae-49e3-b3cb-065f9722b178@intel.com>
Date: Tue, 2 Dec 2025 08:34:10 -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 v14 32/32] x86,fs/resctrl: Update documentation for
telemetry events
Hi Tony,
On 11/24/25 10:54 AM, Tony Luck wrote:
> @@ -484,6 +483,25 @@ with the following files:
> bytes) at which a previously used LLC_occupancy
> counter can be considered for re-use.
>
> +If telemetry monitoring is available there will be a "PERF_PKG_MON" directory
> +with the following files:
> +
> +"num_rmids":
> + The number of RMIDs for telemetry monitoring events. By default,
> + resctrl will not enable telemetry events of a particular type
> + ("perf" or "energy") if the number of RMIDs that can be tracked
> + concurrently for that type is lower than the total number of
> + RMIDs supported by that type. The user can force-enable each
> + type of telemetry events with the "rdt=" boot command line
> + option, but this may reduce the number of monitoring groups that
> + can be created.
v14 changed implementation to no longer disable all events at level of the type.
Reinette
Powered by blists - more mailing lists