lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
 <OSZPR01MB8798C71BC9F3E4370B8A58508BCCA@OSZPR01MB8798.jpnprd01.prod.outlook.com>
Date: Wed, 12 Nov 2025 07:57:45 +0000
From: "Shaopeng Tan (Fujitsu)" <tan.shaopeng@...itsu.com>
To: 'Ben Horgan' <ben.horgan@....com>, "james.morse@....com"
	<james.morse@....com>
CC: "amitsinght@...vell.com" <amitsinght@...vell.com>,
	"baisheng.gao@...soc.com" <baisheng.gao@...soc.com>,
	"baolin.wang@...ux.alibaba.com" <baolin.wang@...ux.alibaba.com>,
	"bobo.shaobowang@...wei.com" <bobo.shaobowang@...wei.com>,
	"carl@...amperecomputing.com" <carl@...amperecomputing.com>,
	"catalin.marinas@....com" <catalin.marinas@....com>, "dakr@...nel.org"
	<dakr@...nel.org>, "dave.martin@....com" <dave.martin@....com>,
	"david@...hat.com" <david@...hat.com>, "dfustini@...libre.com"
	<dfustini@...libre.com>, "fenghuay@...dia.com" <fenghuay@...dia.com>,
	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>, "gshan@...hat.com"
	<gshan@...hat.com>, "guohanjun@...wei.com" <guohanjun@...wei.com>,
	"jeremy.linton@....com" <jeremy.linton@....com>,
	"jonathan.cameron@...wei.com" <jonathan.cameron@...wei.com>,
	"kobak@...dia.com" <kobak@...dia.com>, "lcherian@...vell.com"
	<lcherian@...vell.com>, "lenb@...nel.org" <lenb@...nel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "lpieralisi@...nel.org"
	<lpieralisi@...nel.org>, "peternewman@...gle.com" <peternewman@...gle.com>,
	"quic_jiles@...cinc.com" <quic_jiles@...cinc.com>, "rafael@...nel.org"
	<rafael@...nel.org>, "robh@...nel.org" <robh@...nel.org>,
	"rohit.mathew@....com" <rohit.mathew@....com>, "scott@...amperecomputing.com"
	<scott@...amperecomputing.com>, "sdonthineni@...dia.com"
	<sdonthineni@...dia.com>, "sudeep.holla@....com" <sudeep.holla@....com>,
	"will@...nel.org" <will@...nel.org>, "xhao@...ux.alibaba.com"
	<xhao@...ux.alibaba.com>
Subject: RE: [PATCH 14/33] arm_mpam: Probe hardware to find the supported
 partid/pmg values

> From: James Morse <james.morse@....com>
> 
> CPUs can generate traffic with a range of PARTID and PMG values, but each
> MSC may also have its own maximum size for these fields.
> Before MPAM can be used, the driver needs to probe each RIS on each MSC, to
> find the system-wide smallest value that can be used.
> The limits from requestors (e.g. CPUs) also need taking into account.
> 
> While doing this, RIS entries that firmware didn't describe are created under
> MPAM_CLASS_UNKNOWN.
> 
> This adds the low level MSC write accessors.
> 
> While we're here, implement the mpam_register_requestor() call for the arch
> code to register the CPU limits. Future callers of this will tell us about the
> SMMU and ITS.
> 
> Signed-off-by: James Morse <james.morse@....com>
> Reviewed-by: Jonathan Cameron <jonathan.cameron@...wei.com>
> Reviewed-by: Ben Horgan <ben.horgan@....com>
> Tested-by: Fenghua Yu <fenghuay@...dia.com>
> Tested-by: Shaopeng Tan <tan.shaopeng@...fujitsu.com>
> Tested-by: Peter Newman <peternewman@...gle.com>
> Signed-off-by: Ben Horgan <ben.horgan@....com>
> ---


Reviewed-by: Shaopeng Tan <tan.shaopeng@...fujitsu.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ