From: James Morse <james.morse@arm.com>
To: "Yu, Fenghua" <fenghua.yu@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Chatre, Reinette" <reinette.chatre@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
H Peter Anvin <hpa@zytor.com>, Babu Moger <Babu.Moger@amd.com>,
"shameerali.kolothum.thodi@huawei.com"
<shameerali.kolothum.thodi@huawei.com>,
D Scott Phillips OS <scott@os.amperecomputing.com>,
"carl@os.amperecomputing.com" <carl@os.amperecomputing.com>,
"lcherian@marvell.com" <lcherian@marvell.com>,
"bobo.shaobowang@huawei.com" <bobo.shaobowang@huawei.com>,
"tan.shaopeng@fujitsu.com" <tan.shaopeng@fujitsu.com>,
Jamie Iles <quic_jiles@quicinc.com>,
Xin Hao <xhao@linux.alibaba.com>,
"xingxin.hx@openanolis.org" <xingxin.hx@openanolis.org>,
"baolin.wang@linux.alibaba.com" <baolin.wang@linux.alibaba.com>,
"peternewman@google.com" <peternewman@google.com>
Subject: Re: [PATCH 01/18] x86/resctrl: Track the closid with the rmid
Date: Tue, 10 Jan 2023 17:57:19 +0000 [thread overview]
Message-ID: <54d14a9f-5983-0a33-9340-c0ff48cc9757@arm.com> (raw)
In-Reply-To: <IA1PR11MB609724963D5C6086A98AC0479BFB9@IA1PR11MB6097.namprd11.prod.outlook.com>
Hi Fenghua,
On 06/01/2023 02:57, Yu, Fenghua wrote:
>> James Morse <james.morse@arm.com> writes:
>>
>> x86's RMID are independent of the CLOSID. An RMID can be allocated, used and
>> freed without considering the CLOSID.
>>
>> MPAM's equivalent feature is PMG, which is not an independent number, it
>> extends the CLOSID/PARTID space. For MPAM, only PMG-bits worth of 'RMID'
>> can be allocated for a single CLOSID.
>> i.e. if there is 1 bit of PMG space, then each CLOSID can have two monitor
>> groups.
>>
>> To allow rescrl to disambiguate RMID values for different CLOSID, everything in
>
> s/rescrl/resctrl/
>
>> resctrl that keeps an RMID value needs to know the CLOSID too. This will always
>> be ignored on x86.
>> diff --git a/arch/x86/kernel/cpu/resctrl/internal.h
>> b/arch/x86/kernel/cpu/resctrl/internal.h
>> index 5f7128686cfd..4b243ba88882 100644
>> --- a/arch/x86/kernel/cpu/resctrl/internal.h
>> +++ b/arch/x86/kernel/cpu/resctrl/internal.h
>> @@ -519,7 +519,7 @@ struct rdt_domain *get_domain_from_cpu(int cpu,
>> struct rdt_resource *r); int closids_supported(void); void closid_free(int closid);
>> int alloc_rmid(void); -void free_rmid(u32 rmid);
>> +void free_rmid(u32 closid, u32 rmid);
>> int rdt_get_mon_l3_config(struct rdt_resource *r); void mon_event_count(void
>> *info); int rdtgroup_mondata_show(struct seq_file *m, void *arg); diff --git
>> a/arch/x86/kernel/cpu/resctrl/monitor.c
>> b/arch/x86/kernel/cpu/resctrl/monitor.c
>> index efe0c30d3a12..f1f66c9942a5 100644
>> --- a/arch/x86/kernel/cpu/resctrl/monitor.c
>> +++ b/arch/x86/kernel/cpu/resctrl/monitor.c
>> @@ -25,6 +25,7 @@
>> #include "internal.h"
>>
>> struct rmid_entry {
>> + u32 closid;
>
> Could you please add a comment for this closid field? It's expected to be form x86 RMID entry.
> So it's deserved a comment to explain a bit more on this field.
Sure ... what does it need to convey?
I'm not sure what you mean by "expected to be form x86 RMID entry".
My medium verbosity version looks like this:
| /*
| * Some architectures's resctrl_arch_rmid_read() needs the CLOSID value
| * in order to access the correct monitor. This field provides the
| * value to list walkers like __check_limbo(). On x86 this is ignored.
| */
Does this cover it?
Thanks,
James
>> u32 rmid;
>> int busy;
>> struct list_head list;
next prev parent reply other threads:[~2023-01-10 18:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 13:11 [PATCH 00/18] x86/resctrl: monitored closid+rmid together, separate arch/fs locking James Morse
2022-10-21 13:11 ` [PATCH 01/18] x86/resctrl: Track the closid with the rmid James Morse
2022-10-31 14:42 ` Peter Newman
2022-11-25 4:07 ` haoxin
2023-01-06 2:57 ` Yu, Fenghua
2023-01-10 17:57 ` James Morse [this message]
2023-01-10 18:01 ` Yu, Fenghua
2022-10-21 13:11 ` [PATCH 02/18] x86/resctrl: Access per-rmid structures by index James Morse
2023-01-06 3:12 ` Yu, Fenghua
2023-01-10 17:57 ` James Morse
2022-10-21 13:11 ` [PATCH 03/18] x86/resctrl: Create helper for RMID allocation and mondata dir creation James Morse
2023-01-06 3:23 ` Yu, Fenghua
2023-01-10 17:57 ` James Morse
2022-10-21 13:11 ` [PATCH 04/18] x86/resctrl: Move rmid allocation out of mkdir_rdt_prepare() James Morse
2022-11-10 10:50 ` Shaopeng Tan (Fujitsu)
2022-11-24 14:21 ` James Morse
2022-10-21 13:11 ` [PATCH 05/18] x86/resctrl: Allow RMID allocation to be scoped by CLOSID James Morse
2022-10-21 13:11 ` [PATCH 06/18] x86/resctrl: Allow the allocator to check if a CLOSID can allocate clean RMID James Morse
2022-11-08 15:57 ` Shawn Wang
2022-11-09 17:02 ` James Morse
2022-11-10 10:50 ` Shaopeng Tan (Fujitsu)
2022-11-24 14:21 ` James Morse
2022-10-21 13:11 ` [PATCH 07/18] x86/resctrl: Move CLOSID/RMID matching and setting to use helpers James Morse
2022-11-18 15:49 ` Valentin Schneider
2022-11-24 14:21 ` James Morse
2022-10-21 13:11 ` [PATCH 08/18] x86/resctrl: Queue mon_event_read() instead of sending an IPI James Morse
2022-10-21 13:11 ` [PATCH 09/18] x86/resctrl: Allow resctrl_arch_rmid_read() to sleep James Morse
2022-10-21 13:11 ` [PATCH 10/18] x86/resctrl: Allow arch to allocate memory needed in resctrl_arch_rmid_read() James Morse
2022-10-21 13:11 ` [PATCH 11/18] x86/resctrl: Make resctrl_mounted checks explicit James Morse
2022-10-21 13:11 ` [PATCH 12/18] x86/resctrl: Move alloc/mon static keys into helpers James Morse
2022-10-21 13:11 ` [PATCH 13/18] x86/resctrl: Make rdt_enable_key the arch's decision to switch James Morse
2022-10-21 13:12 ` [PATCH 14/18] x86/resctrl: Add helpers for system wide mon/alloc capable James Morse
2022-11-10 10:51 ` Shaopeng Tan (Fujitsu)
2022-11-24 14:22 ` James Morse
2022-10-21 13:12 ` [PATCH 15/18] x86/resctrl: Add cpu online callback for resctrl work James Morse
2022-10-21 13:12 ` [PATCH 16/18] x86/resctrl: Allow overflow/limbo handlers to be scheduled on any-but cpu James Morse
2022-10-21 13:12 ` [PATCH 17/18] x86/resctrl: Add cpu offline callback for resctrl work James Morse
2022-10-21 13:12 ` [PATCH 18/18] x86/resctrl: Separate arch and fs resctrl locks James Morse
2022-10-31 14:21 ` Peter Newman
2022-11-09 17:18 ` James Morse
2022-11-01 8:01 ` [PATCH 00/18] x86/resctrl: monitored closid+rmid together, separate arch/fs locking Shaopeng Tan (Fujitsu)
2022-11-09 17:21 ` James Morse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54d14a9f-5983-0a33-9340-c0ff48cc9757@arm.com \
--to=james.morse@arm.com \
--cc=Babu.Moger@amd.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=bobo.shaobowang@huawei.com \
--cc=bp@alien8.de \
--cc=carl@os.amperecomputing.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peternewman@google.com \
--cc=quic_jiles@quicinc.com \
--cc=reinette.chatre@intel.com \
--cc=scott@os.amperecomputing.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=tan.shaopeng@fujitsu.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xhao@linux.alibaba.com \
--cc=xingxin.hx@openanolis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®