So long as we can also switch to the emulated GIC when we want/need to :-) (looking at you KVM :-))
Cheers Mark Sent from Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Peter Maydell <peter.mayd...@linaro.org> Sent: Thursday, July 17, 2025 5:36:18 PM To: Danny Canter <danny_can...@apple.com> Cc: Alex Bennée <alex.ben...@linaro.org>; Joelle van Dyne <j...@getutm.app>; Marc Zyngier <m...@kernel.org>; qemu-devel <qemu-devel@nongnu.org>; Alexander Graf <ag...@csgraf.de>; Ynddal <m...@ynddal.dk>; Cameron Esfahani <di...@apple.com>; Roman Bolshakov <rbolsha...@ddn.com>; Phil Dennis-Jordan <p...@philjordan.eu>; Philippe Mathieu-Daudé <phi...@linaro.org>; Richard Henderson <richard.hender...@linaro.org>; Mark Burton <mbur...@qti.qualcomm.com> Subject: Re: HVF EL2 support in QEMU (aka FEAT_NV/FEAT_NV2) for MacOS WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. On Thu, 17 Jul 2025 at 16:16, Danny Canter <danny_can...@apple.com> wrote: > - The new GIC APIs take care of interrupt injection, and would need to be > used in concert with the EL2 APIs if you need interrupt support (highly > likely 😬). This would > be where I’d investigate on the QEMU end first to see if this would fit > within the architecture without a bunch of reworks. > https://developer.apple.com/documentation/hypervisor/hv_gic_create(_:) Ah, Hypervisor.framework supports providing a GIC now? We should definitely switch to using that instead of our userspace fully emulated GICv3 whenever the host supports it. thanks -- PMM
