linux-kernel - RE: [PATCH v2] arm64: dts: add cpu cache information to ExynosAuto-v920

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <090c01db77e7$ffa892b0$fef9b810$@samsung.com>
Date: Wed, 5 Feb 2025 21:37:02 +0530
From: "Alim Akhtar" <alim.akhtar@...sung.com>
To: "'Sudeep Holla'" <sudeep.holla@....com>
Cc: "'Devang Tailor'" <dev.tailor@...sung.com>, <robh@...nel.org>,
	<krzk+dt@...nel.org>, <conor+dt@...nel.org>, <devicetree@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>, <linux-samsung-soc@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <faraz.ata@...sung.com>
Subject: RE: [PATCH v2] arm64: dts: add cpu cache information to
 ExynosAuto-v920

Hi Sudeep 

> -----Original Message-----
> From: Sudeep Holla <sudeep.holla@....com>
> Sent: Friday, January 31, 2025 6:57 PM
> To: Alim Akhtar <alim.akhtar@...sung.com>
> Cc: 'Devang Tailor' <dev.tailor@...sung.com>; robh@...nel.org;
> krzk+dt@...nel.org; conor+dt@...nel.org; devicetree@...r.kernel.org;
> linux-arm-kernel@...ts.infradead.org; linux-samsung-soc@...r.kernel.org;
> linux-kernel@...r.kernel.org; faraz.ata@...sung.com
> Subject: Re: [PATCH v2] arm64: dts: add cpu cache information to
> ExynosAuto-v920
> 
[snip]
> > You can add one node for cl0 and cl1, say "l3_cache_cl0_cl1" and
> > Remove the specific node for CL1, because both are same.
> >
> 
> What do you mean by "both are same" ?
> Do you mean both have exact same properties but are physically different
> caches ? OR Do you mean it is just one shared cache ?
> 
Thanks for review and pointing it out, v920 has physically different caches 
(two of them are same properties, but the 3rd has 1MB lesser size)
Got you point about having distinct node for cacheinfo population
So for this patch:

Reviewed-by: Alim Akhtar <alim.akhtar@...sung.com>

> If former, we still need distinct node to get the cacheinfo about
shareability
> correct. If this is about avoiding duplication of errors, you can probably
define
> some macro and avoid it, but we need 2 nodes in the devicetree.
> 
> If latter, you suggestion is correct.
> 
> --
> Regards,
> Sudeep