[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB60837B532254E7B23BC27E84FC052@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Wed, 18 Dec 2024 23:27:11 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Babu Moger <babu.moger@....com>, "Chatre, Reinette"
<reinette.chatre@...el.com>, "tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>, "bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>
CC: "Yu, Fenghua" <fenghua.yu@...el.com>, "x86@...nel.org" <x86@...nel.org>,
"hpa@...or.com" <hpa@...or.com>, "akpm@...ux-foundation.org"
<akpm@...ux-foundation.org>, "paulmck@...nel.org" <paulmck@...nel.org>,
"thuth@...hat.com" <thuth@...hat.com>, "rostedt@...dmis.org"
<rostedt@...dmis.org>, "xiongwei.song@...driver.com"
<xiongwei.song@...driver.com>, "pawan.kumar.gupta@...ux.intel.com"
<pawan.kumar.gupta@...ux.intel.com>, "jpoimboe@...nel.org"
<jpoimboe@...nel.org>, "daniel.sneddon@...ux.intel.com"
<daniel.sneddon@...ux.intel.com>, "thomas.lendacky@....com"
<thomas.lendacky@....com>, "perry.yuan@....com" <perry.yuan@....com>,
"sandipan.das@....com" <sandipan.das@....com>, "Huang, Kai"
<kai.huang@...el.com>, "seanjc@...gle.com" <seanjc@...gle.com>, "Li, Xin3"
<xin3.li@...el.com>, "ebiggers@...gle.com" <ebiggers@...gle.com>,
"andrew.cooper3@...rix.com" <andrew.cooper3@...rix.com>,
"mario.limonciello@....com" <mario.limonciello@....com>,
"tan.shaopeng@...itsu.com" <tan.shaopeng@...itsu.com>, "james.morse@....com"
<james.morse@....com>, "peternewman@...gle.com" <peternewman@...gle.com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Eranian,
Stephane" <eranian@...gle.com>, "corbet@....net" <corbet@....net>
Subject: RE: [PATCH v2 0/7] x86/resctrl : Support L3 Smart Data Cache
Injection Allocation Enforcement (SDCIAE)
I don't have an AMD system, so I added a couple of hacks to the code to pretend I did.
My hacks might have missed something, so the below test may not fail for you.
My test:
# echo 1 > info/L3/io_alloc
# cat info/L3/bit_usage
This gave me a console splat starting with:
[ 163.801078] invalid mode for closid 14
That happened because in rdt_bit_usage_show()
for (i = 0; i < closids_supported(); i++) {
if (!closid_allocated(i))
continue;
ctrl_val = resctrl_arch_get_config(r, dom, i,
s->conf_type);
mode = rdtgroup_mode_by_closid(i);
CLOSID 14 is my highest. It's supported, and allocated.
rdtgroup_mode_by_closid() searches rdt_all_groups to find
one using CLOSID 14, but there isn't one. So it returns
RDT_NUM_MODES
Maybe RDT_NUM_MODES isn't invalid in the switch()
Looks like it should be same action as RDT_MODE_SHAREABLE?
-Tony
Powered by blists - more mailing lists