[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zhfy7dmFBf3yLkiA@e133380.arm.com>
Date: Thu, 11 Apr 2024 15:25:49 +0100
From: Dave Martin <Dave.Martin@....com>
To: Reinette Chatre <reinette.chatre@...el.com>
Cc: James Morse <james.morse@....com>, x86@...nel.org,
linux-kernel@...r.kernel.org, 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>
Subject: Re: [PATCH v1 27/31] x86/resctrl: Rename resctrl_sched_in() to begin
resctrl_arch_
On Mon, Apr 08, 2024 at 08:26:04PM -0700, Reinette Chatre wrote:
> Hi James,
>
> In subject, did you intend to say "to begin with"?
I'd say the subject is likely to be abbreviated rather than incorrect,
but it certainly does no harm to clarify it. I'll make a note.
> On 3/21/2024 9:51 AM, James Morse wrote:
> > resctrl_sched_in() loads the architecture specific CPU MSRs with the
> > CLOSID and RMID values. This function was named before resctrl was
> > split to have architecture specific code, and generic filesystem code.
> >
> > This function is obviously architecture specific, but does not begin
> > with 'resctrl_arch_', making it the odd one out in the functions an
> > architecture needs to support to enable resctrl.
> >
> > Rename it for concistency. This is purely cosmetic.
>
> concistency -> consistency
Noted.
Cheers
---Dave
Powered by blists - more mailing lists