[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <479ea81d-024a-5a7e-f045-4de52e97a599@intel.com>
Date: Thu, 15 Jun 2023 16:28:40 -0700
From: Reinette Chatre <reinette.chatre@...el.com>
To: James Morse <james.morse@....com>, <x86@...nel.org>,
<linux-kernel@...r.kernel.org>
CC: Fenghua Yu <fenghua.yu@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
H Peter Anvin <hpa@...or.com>,
Babu Moger <Babu.Moger@....com>,
<shameerali.kolothum.thodi@...wei.com>,
D Scott Phillips OS <scott@...amperecomputing.com>,
<carl@...amperecomputing.com>, <lcherian@...vell.com>,
<bobo.shaobowang@...wei.com>, <tan.shaopeng@...itsu.com>,
<xingxin.hx@...nanolis.org>, <baolin.wang@...ux.alibaba.com>,
Jamie Iles <quic_jiles@...cinc.com>,
Xin Hao <xhao@...ux.alibaba.com>, <peternewman@...gle.com>,
<dfustini@...libre.com>
Subject: Re: [PATCH v4 00/24] x86/resctrl: monitored closid+rmid together,
separate arch/fs locking
Hi James,
On 5/25/2023 11:01 AM, James Morse wrote:
>
> The second part of this series adds a domain_list_lock to protect writes to the
> domain list, and protects the domain list with RCU - or read_cpus_lock().
read_cpus_lock() -> cpus_read_lock()
>
> Use of RCU is to allow lockless readers of the domain list, today resctrl only has
> one, rdt_bit_usage_show(). But to get MPAMs monitors working, its very likely
This may need an update to reflect changes since initial version (similar to the
relevant patch).
Reinette
Powered by blists - more mailing lists