[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <34446657-4b03-416e-a8be-fcf35e3419fe@intel.com>
Date: Fri, 25 Jul 2025 16:17:59 -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 v7 05/31] x86,fs/resctrl: Improve domain type checking
Hi Tony,
On 7/11/25 4:53 PM, Tony Luck wrote:
> The rdt_domain_hdr structure is used in both control and monitor
> domain structures to provide common methods for operations such as
> adding a CPU to a domain, removing a CPU from a domain, accessing
> the mask of all CPUs in a domain.
>
> The "type" field provides a simple check whether a domain is a
> control or monitor domain so that programming errors operating
> on domains will be quickly caught.
Above is context.
Below is a mixup of problem and solution. Please separate these clearly.
> To prepare for additional domain types that depend on the rdt_resource
If "rdt_resource" refers to the struct then please "struct rdt_resource".
If it instead just refers to the concept of a resource, just "resource".
> to which they are connected add the resource id into the header
> and check that in addition to the type.
>
> Signed-off-by: Tony Luck <tony.luck@...el.com>
> ---
Reinette
Powered by blists - more mailing lists