[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9479c799-86fc-4d9e-addb-66011ecae9c7@arm.com>
Date: Mon, 7 Oct 2024 18:29:32 +0100
From: James Morse <james.morse@....com>
To: Reinette Chatre <reinette.chatre@...el.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,
baolin.wang@...ux.alibaba.com, Jamie Iles <quic_jiles@...cinc.com>,
Xin Hao <xhao@...ux.alibaba.com>, peternewman@...gle.com,
dfustini@...libre.com, amitsinght@...vell.com,
David Hildenbrand <david@...hat.com>, Rex Nie <rex.nie@...uarmicro.com>,
Dave Martin <dave.martin@....com>
Subject: Re: [PATCH v5 00/40] x86/resctrl: Move the resctrl filesystem code to
/fs/resctrl
Hi Reinette,
On 04/10/2024 22:18, Reinette Chatre wrote:
> While you wait for folks to consider these changes, could you please take a look
> at [1] from an Arm/MPAM perspective? My understanding is that Arm/MPAM also
> requires assigning counters to do monitoring and [1] aims to create
> a generic interface to do so. Is [1] something that Arm/MPAM can build on
> or are there some changes that can be made before its inclusion to help
> with future MPAM support?
Yup, this is on my list to get back into this week.
I did rebase the MPAM tree over Babu's v6, but haven't had the chance to test it [0].
This is my previous feedback on where the arch/fs split needed to be came form.
Thanks,
James
[0] https://git.kernel.org/pub/scm/linux/kernel/git/morse/linux.git/log/?h=mpam/abmc/v6
Powered by blists - more mailing lists