From: James Morse <james.morse@arm.com>
To: Valentin Schneider <vschneid@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Fenghua Yu <fenghua.yu@intel.com>,
Reinette Chatre <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,
D Scott Phillips OS <scott@os.amperecomputing.com>,
carl@os.amperecomputing.com, lcherian@marvell.com,
bobo.shaobowang@huawei.com, tan.shaopeng@fujitsu.com,
Jamie Iles <quic_jiles@quicinc.com>,
Xin Hao <xhao@linux.alibaba.com>,
xingxin.hx@openanolis.org, baolin.wang@linux.alibaba.com,
peternewman@google.com
Subject: Re: [PATCH 07/18] x86/resctrl: Move CLOSID/RMID matching and setting to use helpers
Date: Thu, 24 Nov 2022 14:21:25 +0000 [thread overview]
Message-ID: <7a942c00-67a9-c038-b516-4ae85e997a6e@arm.com> (raw)
In-Reply-To: <xhsmh8rk8xnxg.mognet@vschneid.remote.csb>
Hi Valentin,
On 18/11/2022 15:49, Valentin Schneider wrote:
> On 21/10/22 13:11, James Morse wrote:
>> When switching tasks, the CLOSID and RMID that the new task should
>> use are stored in struct task_struct. For x86 the CLOSID known by resctrl,
>> the value in task_struct, and the value written to the CPU register are
>> all the same thing.
>>
>> MPAM's CPU interface has two different PARTID's one for data accesses
>> the other for instruction fetch. Storing resctrl's CLOSID value in
>> struct task_struct implies the arch code knows whether resctrl is using
>> CDP.
>>
>> Move the matching and setting of the struct task_struct properties
>> to use helpers. This allows arm64 to store the hardware format of
>> the register, instead of having to convert it each time.
>>
>> __rdtgroup_move_task()s use of READ_ONCE()/WRITE_ONCE() ensures torn
>> values aren't seen as another CPU may schedule the task being moved
>> while the value is being changed. MPAM has an additional corner-case
>> here as the PMG bits extend the PARTID space. If the scheduler sees a
>> new-CLOSID but old-RMID, the task will dirty an RMID that the limbo code
>> is not watching causing an inaccurate count. x86's RMID are independent
>> values, so the limbo code will still be watching the old-RMID in this
>> circumstance.
>> To avoid this, arm64 needs both the CLOSID/RMID WRITE_ONCE()d together.
>> Both values must be provided together.
> I think I remember something about this... Is that about having them
> union'd and read/written as one? (just for my own curiosity)
Yup. Many moons ago you pointed out that storing partid/pmg separately lets the remote
CPUs load torn values. arm64 not only needs the values as a pair, it needs to read/write
them as a pair.
>> Because MPAM's RMID values are not unique, the CLOSID must be provided
>> when matching the RMID.
>>
>> CC: Valentin Schneider <vschneid@redhat.com>
(CC here also stands for celebrate-contribution!)
>> Signed-off-by: James Morse <james.morse@arm.com>
>
> Reviewed-by: Valentin Schneider <vschneid@redhat.com>
Thanks!
James
next prev parent reply other threads:[~2022-11-24 14:21 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
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 [this message]
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=7a942c00-67a9-c038-b516-4ae85e997a6e@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=vschneid@redhat.com \
--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®