On Mon, Nov 14, 2022 at 02:08:45PM +0000, Catalin Marinas wrote:

> I'm not even sure how we could work around this in the kernel. There's
> no meaningful MIDR to probe, nor do we know which macOS version it is
> running on. The best we could do is put some #ifdef CONFIG_ARM64_SME
> around the ID_AA64SMFR0_EL1 access but defconfig and most distros would
> probably have the option on anyway.

There should be some firmware information we have access to early
enough, hopefully some of it might allow us to determine if it's
an affected system but I'd expect that by the time we figure
something out and deploy it most users will have upgraded anyway.