Re: [PATCH v8 10/32] x86,fs/resctrl: Rename struct rdt_mon_domain and rdt_hw_mon_domain

[Reinette Chatre]

Hi Tony,

On 8/11/25 11:16 AM, Tony Luck wrote:
> All monitoring events are associated with the L3 resource.

With a bit more context:
	All monitoring events are associated with the L3 resource.
	The per L3 domain resctrl fs monitoring state is maintained in the
	generically named struct rdt_mon_domain while the per L3 domain
	architecture specific monitoring state is maintained                       
	in the generically named struct rdt_hw_mon_domain.

> 
> This will change when support for telemetry events is added.

	Upcoming telemetry event monitoring will be tied to another resource
	and requires new domain structures. 

> 
> The structures to track monitor domains of the L3 resource at both the
> file system and architecture level have generic names. This may cause
> confusion when support for monitoring events in other resources is added.

	Rename the L3 resource specific domain data structures to include
	"l3_" in their names to avoid confusion between the different
	resource specific domain structures:
	rdt_mon_domain		-> rdt_l3_mon_domain
	rdt_hw_mon_domain	-> rdt_hw_l3_mon_domain
> 
> Rename by adding "l3_" into the names:
> rdt_mon_domain		-> rdt_l3_mon_domain
> rdt_hw_mon_domain	-> rdt_hw_l3_mon_domain
> 
> No functional change.
> 
> Signed-off-by: Tony Luck <tony.luck@xxxxxxxxx>
> ---

Running "git grep rdt_mon_domain" with this series applied found one more spot
that needs to switch:
arch/x86/kernel/cpu/resctrl/monitor.c: * nodes that share an L3 cache). Linux creates an rdt_mon_domain for

Reinette