[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 5 May 2023 16:20:56 -0700
From: Reinette Chatre <reinette.chatre@...el.com>
To: Tony Luck <tony.luck@...el.com>, Fenghua Yu <fenghua.yu@...el.com>,
"Thomas Gleixner" <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"Borislav Petkov" <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>,
Shaopeng Tan <tan.shaopeng@...itsu.com>,
Jamie Iles <quic_jiles@...cinc.com>,
James Morse <james.morse@....com>,
Babu Moger <babu.moger@....com>
CC: <x86@...nel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 6/7] x86/resctrl: Allow a device to override an
existing schemata entry
Hi Tony,
On 4/20/2023 3:06 PM, Tony Luck wrote:
> Remove that entry from the resctrl_schema_all list when driver
> is loaded. Put it back again when driver is unloaded.
This is unexpected. It sounds like the system would advertise
a supported resource with appropriate properties but for some reason this
is not correct, optional in some way, or perhaps resources are
conflicting? Where would it be decided whether the overriding driver
should be loaded and why can that logic not be in enumeration
within resctrl?
Reinette
Powered by blists - more mailing lists