Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Reeves via B4 Relay <devnull+michael.reeves077.gmail.com@kernel.org>
To: Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>,
	 Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	 Mark Rutland <mark.rutland@arm.com>
Cc: Myria Sarvay <myrialsarvay@gmail.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,
	 Michael Reeves <michael.reeves077@gmail.com>
Subject: [PATCH 0/2] arm64: Add support for Apple M3 and M4 CPUs in KVM
Date: Thu, 08 Oct 2026 23:15:39 +1100	[thread overview]
Message-ID: <20261008-apple-m3-m4-kvm-v1-0-7bb4cbf3d63b@gmail.com> (raw)

Hi,

This series enables KVM support on Apple Silicon M3 series and base M4
CPUs.

The first patch adds the part numbers and MIDR definitions for M3
(base, Pro and Max) and base M4 CPU cores.

The second patch adds these CPUs to the existing Apple CPU workarounds
list, which is required for KVM to function correctly.

This series was developed from testing on:
- Apple M3 and M3 Pro by Michael Reeves
- Apple M3 Max by Myria Sarvay and Yureka Lilian
- Apple M4 by Yureka Lilian

---
Michael Reeves (1):
      arm64: Apply existing Apple CPU workarounds to M3 and M4

Myria Sarvay (1):
      arm64: Add Apple M3 and M4 CPU part numbers

 arch/arm64/include/asm/cputype.h | 16 ++++++++++++++++
 arch/arm64/kernel/cpu_errata.c   |  8 ++++++++
 2 files changed, 24 insertions(+)
---
base-commit: a90ee4305c4a5df72c11b31dacfdc76e00fcf78a
change-id: 20261008-apple-m3-m4-kvm-b7b9b2e34bcd

Best regards,
--  
Michael Reeves <michael.reeves077@gmail.com>




             reply	other threads:[~2026-10-08 12:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 12:15 Michael Reeves via B4 Relay [this message]
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

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=20261008-apple-m3-m4-kvm-v1-0-7bb4cbf3d63b@gmail.com \
    --to=devnull+michael.reeves077.gmail.com@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=maz@kernel.org \
    --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