From: Marc Zyngier <maz@kernel.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Alexander Graf" <agraf@csgraf.de>, Ynddal <mads@ynddal.dk>,
"Cameron Esfahani" <dirty@apple.com>,
"Roman Bolshakov" <rbolshakov@ddn.com>,
"Phil Dennis-Jordan" <phil@philjordan.eu>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Mark Burton" <mburton@qti.qualcomm.com>,
"Joelle van Dyne" <j@getutm.app>,
"Danny Canter" <danny_canter@apple.com>
Subject: Re: HVF EL2 support in QEMU (aka FEAT_NV/FEAT_NV2) for MacOS
Date: Tue, 15 Jul 2025 12:51:27 +0100 [thread overview]
Message-ID: <86wm898yf4.wl-maz@kernel.org> (raw)
In-Reply-To: <87zfd5zouv.fsf@draig.linaro.org>
On Tue, 15 Jul 2025 12:15:52 +0100,
Alex Bennée <alex.bennee@linaro.org> wrote:
> - do we know which Apple silicon supports FEAT_NV2?
M2 and latter definitely support FEAT_NV2. That's how KVM NV support
has been developed for two years until I was given better HW.
Whether Apple supports NV on M2 in HVF, I have no idea. The rumour
mill says "no", but I don't have a way to check. The M3 I use at $WORK
is definitely able to give me EL2 without VHE with UTM. I haven't
played with M4, but I have it on the record that it behaves like M3
with UTM.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-07-15 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 11:15 HVF EL2 support in QEMU (aka FEAT_NV/FEAT_NV2) for MacOS Alex Bennée
2025-07-15 11:51 ` Marc Zyngier [this message]
2025-07-15 15:53 ` Joelle van Dyne
2025-07-16 7:27 ` Danny Canter
2025-07-16 12:17 ` Alex Bennée
2025-07-17 15:16 ` Danny Canter
2025-07-17 15:36 ` Peter Maydell
2025-07-17 15:45 ` Mark Burton
2025-07-17 16:13 ` Marc Zyngier
2025-07-17 16:15 ` Mark Burton
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=86wm898yf4.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=agraf@csgraf.de \
--cc=alex.bennee@linaro.org \
--cc=danny_canter@apple.com \
--cc=dirty@apple.com \
--cc=j@getutm.app \
--cc=mads@ynddal.dk \
--cc=mburton@qti.qualcomm.com \
--cc=peter.maydell@linaro.org \
--cc=phil@philjordan.eu \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rbolshakov@ddn.com \
--cc=richard.henderson@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.