linux-kernel - Re: [PATCH v3 0/5] MIPS: Allow using multi-cluster with a broken HCI.

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] [day] [month] [year] [list]

Message-ID: <Z7iH83W6Og2AA92f@alpha.franken.de>
Date: Fri, 21 Feb 2025 15:04:35 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Gregory CLEMENT <gregory.clement@...tlin.com>
Cc: Aleksandar Rikalo <arikalo@...il.com>,
	Jiaxun Yang <jiaxun.yang@...goat.com>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Vladimir Kondratiev <vladimir.kondratiev@...ileye.com>,
	Théo Lebrun <theo.lebrun@...tlin.com>,
	Tawfik Bayouk <tawfik.bayouk@...ileye.com>,
	Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
	linux-mips@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/5] MIPS: Allow using multi-cluster with a broken HCI.

On Thu, Jan 23, 2025 at 12:01:53PM +0100, Gregory CLEMENT wrote:
> Hello,
> 
> Some CM3.5 reports indicate that Hardware Cache Initialization is
> complete, but in reality it's not the case. They also incorrectly show
> that Hardware Cache Initialization is supported. Unfortunately, it is
> not possible to detect this issue at runtime and the information has
> to be passed by the device tree.
> 
> In this third version, I rebased on v6.13. I also addressed remarks
> made by Rob and Krzysztof, and endeavored to add more explanation
> about CM, explaining why we now need to represent it in the device
> tree.
> 
> My initial proposal was integrated into the series set by Aleksandar
> here [1]. And the series adding the CM binding was here: [2]. The
> patches 1,2,3, and 5 have no dependencies while patch 4 should depend
> on this series [1]. Actually, those five patches should replace
> patches 10, 11, and 12.
> 
> Gregory
> 
> [1]: https://lore.kernel.org/all/20241028175935.51250-1-arikalo@gmail.com/
> [2]: https://lore.kernel.org/all/20240612-cm_probe-v2-5-a5b55440563c@flygoat.com/
> 
> Signed-off-by: Gregory CLEMENT <gregory.clement@...tlin.com>
> ---
> Changes in v3:
> - Provide a more detailed explanation about the CM in the device tree binding.
> - Make the reg property optional for all compatible strings.
> - Use "mobileye" instead of "mti" for the eyeq6-cm compatible string.
> - Address and correct the formatting issues in example and description.
> - Link to v2: https://lore.kernel.org/r/20250116-cluster-hci-broken-v2-0-fc52cfb7a19e@bootlin.com
> 
> Changes in v2:
> - Use compatible string instead of property
> - Link to v1: https://lore.kernel.org/r/20241115-cluster-hci-broken-v1-0-00636800611d@bootlin.com
> 
> ---
> Gregory CLEMENT (5):
>       dt-bindings: mips: Document mti,mips-cm
>       dt-bindings: mips: mips-cm: Add a new compatible string for EyeQ6
>       MIPS: cm: Detect CM quirks from device tree
>       MIPS: CPS: Support broken HCI for multicluster
>       MIPS: mobileye: dts: eyeq6h: Enable cluster support
> 
>  .../devicetree/bindings/mips/mti,mips-cm.yaml      | 57 ++++++++++++++++++++++
>  arch/mips/boot/dts/mobileye/eyeq6h.dtsi            |  4 ++
>  arch/mips/include/asm/mips-cm.h                    | 22 +++++++++
>  arch/mips/kernel/mips-cm.c                         | 14 ++++++
>  arch/mips/kernel/smp-cps.c                         |  5 +-
>  5 files changed, 101 insertions(+), 1 deletion(-)

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]