[QUESTION ]ARM64 external L3 cache support in topology info
From: Shameerali Kolothum Thodi <hidden>
Date: 2016-02-05 15:33:55
-----Original Message----- From: Sudeep Holla [mailto:sudeep.holla at arm.com] Sent: Friday, February 05, 2016 2:30 PM To: Shameerali Kolothum Thodi; linux-arm-kernel at lists.infradead.org Cc: Sudeep Holla Subject: Re: [QUESTION ]ARM64 external L3 cache support in topology info [..]quoted
In our case, the L3 cache seems to be intelligent enough and doesn't require any additional maintenance ops. So there is no cache-controllerquoted
code for this. I am just wondering what's the best way to add this L3 cache info to the topology. Overriding the CLIDR register, if thereisquoted
a next-level-cache entry in the dts and then retrieve the cachegeometryquoted
either from dts or from cache specific registers( but this will be implementation specific) ? Or am I missing something here?Recent discussion on this [1] made it clear that we need to support overriding cache properties using DT for some designs. I will consider this "transparent" external/system level cache when I look into moving PPC DT code in generic cacheinfo. I am not sure if it's OK to support mixed information source for a platform(all internal caches via CLIDR and external ones via DT), but we can pick up discussion once we I have the patch.
Ok. Will wait for that then. Thanks.
-- Regards, Sudeep [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015- October/381758.html