Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH v5 00/10] x86/resctrl: Misc cleanup
To:     Reinette Chatre <reinette.chatre@intel.com>
Cc:     x86@kernel.org, linux-kernel@vger.kernel.org,
        Fenghua Yu <fenghua.yu@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>
References: <20200708163929.2783-1-james.morse@arm.com>
From:   James Morse <james.morse@arm.com>
Message-ID: <1887b64a-dd18-25ff-a9f4-885c231c60b2@arm.com>
Date:   Thu, 23 Jul 2020 19:31:52 +0100
User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <20200708163929.2783-1-james.morse@arm.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.