Hi,
On 09/12/2018 09:41 AM, Jeffrey Hugo wrote:
The HW designers have indicated that there is no sane way to provide
sets/ways information to software, even on an informational basis (ie
not for cache maintenance, but for performance optimizations). Therefore
the firmware will not provide this information because it will be wrong.
So, therefore, we should still be able to tell the user that a cache
exists at the relevant level, and what size it is. On the concerned
system, we cannot do that currently.
Ok, so set the fields to zero in firmware node, and mark them valid.
That logically says that there isn't any set/way information for the
cache (which implies direct mapped).
