[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <882ae5f2-08a2-4d7e-ac9f-088c7b3f241f@intel.com>
Date: Tue, 8 Jul 2025 15:05:35 -0700
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>, Anil Keshavamurthy <anil.s.keshavamurthy@...el.com>,
Chen Yu <yu.c.chen@...el.com>
CC: <x86@...nel.org>, <linux-kernel@...r.kernel.org>,
<patches@...ts.linux.dev>
Subject: Re: [PATCH v6 16/30] x86,fs/resctrl: Add and initialize rdt_resource
for package scope core monitor
Hi Tony,
On 6/26/25 9:49 AM, Tony Luck wrote:
> Counts for each Intel telemetry event are periodically sent to one or
> more aggregators on each package where accumulated totals are made
> available in MMIO registers.
>
> Add a new resource for monitoring these events so that CPU hotplug
> notifiers will build domains at the package granularity.
Patch does a bit more than this. This can be expanded to:
Add a new PERF_PKG resource and introduce package level scope for monitoring
these events so that CPU hotplug notifiers can build domains at the package
granularity.
Use the physical package ID available via topology_physical_package_id()
to identify the monitoring domains with package level scope. This enables
user space to use /sys/devices/system/cpu/cpuX/topology/physical_package_id
to identify the monitoring domain a CPU is associated with.
(Please always feel free to improve.)
>
> Signed-off-by: Tony Luck <tony.luck@...el.com>
> ---
Patch looks good to me.
Reinette
Powered by blists - more mailing lists