[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1887b64a-dd18-25ff-a9f4-885c231c60b2@arm.com>
Date: Thu, 23 Jul 2020 19:31:52 +0100
From: James Morse <james.morse@....com>
To: Reinette Chatre <reinette.chatre@...el.com>
Cc: 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>
Subject: Re: [PATCH v5 00/10] x86/resctrl: Misc cleanup
Hi Reinette,
On 08/07/2020 17:39, James Morse wrote:
> These are the miscellaneous cleanup patches that floated to the top of
> the MPAM tree.
Is there anything else I should do with this series?
(Does patch 10 need an ACK from anyone else?)
Would a branch or pull request make anyone's life easier?
Thanks,
James
> The only interesting thing are the patches to make the AMD/Intel
> differences something resctrl understands, instead of just 'happening'
> because of the different function pointers.
> This will become more important once MPAM support is added. parse_bw()
> and friends are what enforces resctrl's ABI. Allowing an
> architecture/platform to provide a subtly different function here would
> be bad for user-space.
>
> MPAM would set arch_has_sparse_bitmaps and arch_has_empty_bitmap, but
> not arch_needs_linear.
> Nothing in this series should change any behaviour.
Powered by blists - more mailing lists