From: Marc Zyngier <maz@kernel.org>
To: Mark Burton <mburton@qti.qualcomm.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Danny Canter" <danny_canter@apple.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Joelle van Dyne" <j@getutm.app>,
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>
Subject: Re: HVF EL2 support in QEMU (aka FEAT_NV/FEAT_NV2) for MacOS
Date: Thu, 17 Jul 2025 17:13:11 +0100 [thread overview]
Message-ID: <86tt3a94o8.wl-maz@kernel.org> (raw)
In-Reply-To: <CO1PR02MB86174C98FACECFFD6116231B8F51A@CO1PR02MB8617.namprd02.prod.outlook.com>
On Thu, 17 Jul 2025 16:45:37 +0100,
Mark Burton <mburton@qti.qualcomm.com> wrote:
>
> So long as we can also switch to the emulated GIC when we want/need
> to :-) (looking at you KVM :-))
KVM really doesn't need such a non-feature. Specially as it cannot be
implemented without an actual GICv3 in HW, for obvious reasons.
My not-so-secret plan is to eventually deprecate the userspace
interface anyway, as it has been bitrotting for quite some time, and
can be replaced with an in-kernel GICv2 emulation.
But this is getting majorly off-topic in this thread...
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-07-17 19:08 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
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 [this message]
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=86tt3a94o8.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.