From: Marc Zyngier <maz@kernel.org>
To: Myria Sarvay <myrialsarvay@gmail.com>
Cc: Michael Reeves <michael.reeves077@gmail.com>,
Oliver Upton <oupton@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Yureka Lilian <yureka@cyberchaos.dev>,
Fuad Tabba <fuad.tabba@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
Sven Peter <sven@kernel.org>, Janne Grunau <j@jannau.net>,
Neal Gompa <neal@gompa.dev>,
asahi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: Apply existing Apple CPU workarounds to M3 and M4
Date: Sat, 10 Oct 2026 12:10:30 +0100 [thread overview]
Message-ID: <864iet3j6h.wl-maz@kernel.org> (raw)
In-Reply-To: <asoZWBEEEsFD5Qrn@macbookair>
On Sat, 10 Oct 2026 11:54:16 +0100,
Myria Sarvay <myrialsarvay@gmail.com> wrote:
>
> Hi Marc,
>
> (Resending because I forgot to reply all, sorry Marc)
>
> On Fri, Oct 09, 2026 at 09:16:03AM +0100, Marc Zyngier wrote:
> > On Fri, 09 Oct 2026 01:03:57 +0100,
> > Michael Reeves <michael.reeves077@gmail.com> wrote:
> > >
> > > > I can provide the binary (and a few scripts) to test this easily.
> > > > Should they have been fixed, we can always create a second
> > > > implementation list to cover the PMU.
> > >
> > > Can you please send that so we can try? That would be much
> > > appreciated, thank you.
> >
> > I've sent you (and Yureka) details over IRC. If you need help with
> > setting things up, let me know directly.
> >
> > Thanks,
> >
> > M.
> >
> > --
> > Without deviation from the norm, progress is not possible.
>
> I've tested the patches on my M3 Max (t6031-j514c), and without these
> patches, it SErrors, and with them (and including the M3/M4 MIDRs in
> the has_vgic_v3 list in arch/arm64/kernel/cpufeature.c) it doesn't
> SError, and the iso boots correctly to a login getty.
Thanks for letting me know.
When you post v2 to fix the has_vgic_v3 list, please collect the
details of what this was tested on in the cover letter, it may become
useful in the future.
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2026-10-10 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 12:15 [PATCH 0/2] arm64: Add support for Apple M3 and M4 CPUs in KVM Michael Reeves via B4 Relay
2026-10-08 12:15 ` [PATCH 1/2] arm64: Add Apple M3 and M4 CPU part numbers Michael Reeves via B4 Relay
2026-10-08 12:15 ` [PATCH 2/2] arm64: Apply existing Apple CPU workarounds to M3 and M4 Michael Reeves via B4 Relay
2026-10-08 13:19 ` Marc Zyngier
2026-10-09 0:03 ` Michael Reeves
2026-10-09 8:16 ` Marc Zyngier
2026-10-10 10:54 ` Myria Sarvay
2026-10-10 11:10 ` Marc Zyngier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=864iet3j6h.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=asahi@lists.linux.dev \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=j@jannau.net \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michael.reeves077@gmail.com \
--cc=myrialsarvay@gmail.com \
--cc=neal@gompa.dev \
--cc=oupton@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=sven@kernel.org \
--cc=will@kernel.org \
--cc=yureka@cyberchaos.dev \
--cc=yuzenghui@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox