[PATCH v4 3/3] arm64: paravirt: Enable errata based on implementation CPUs
Marc Zyngier
maz at kernel.org
Fri Dec 20 03:17:00 PST 2024
On Thu, 19 Dec 2024 17:40:55 +0000,
Oliver Upton <oliver.upton at linux.dev> wrote:
>
> > Independent of this, I wonder what we should output in sysfs
> > (/sys/devices/system/cpu/cpu*/regs/identification/*).
>
> It's a bit crap, but maybe implementation index 0 gets reported through
> the 'main' midr/revidr files, otherwise have a directory per
> implementation index of midr/revidr.
Having slept on that one, I'm starting to think that we should keep
the status-quo of reporting what the kernel snapshot at boot time.
There is no good reason to force the VMM to report the potential
implementations in any specific order.
The "alternative-implementations" is interesting, but we don't keep it
per-CPU, so I don't think it fits the current scheme. But maybe
something in /sys/devices/system/cpu, outside of the cpu* hierarchy?
Either way, this isn't something we should worry too much right now.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
More information about the linux-arm-kernel
mailing list