From: Akihiko Odaki <odaki@rsg.ci.i.u-tokyo.ac.jp>
To: Mohamed Mediouni <mohamed@unpredictable.fr>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
"Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Phil Dennis-Jordan" <phil@philjordan.eu>,
"Peter Xu" <peterx@redhat.com>, "Mads Ynddal" <mads@ynddal.dk>,
"Roman Bolshakov" <rbolshakov@ddn.com>,
"Alexander Graf" <agraf@csgraf.de>
Subject: Re: [RFC PATCH v7 7/7] hvf: do not merge: enable private ISA
Date: Wed, 25 Mar 2026 21:20:09 +0900 [thread overview]
Message-ID: <a273d3e3-4fcf-4969-b43c-4dadb94ea2c9@rsg.ci.i.u-tokyo.ac.jp> (raw)
In-Reply-To: <78785F86-CA85-4187-93A6-1D9852263964@unpredictable.fr>
On 2026/03/25 20:21, Mohamed Mediouni wrote:
>
>> On 25. Mar 2026, at 12:07, Akihiko Odaki <odaki@rsg.ci.i.u-tokyo.ac.jp> wrote:
>>
>> On 2026/03/25 5:48, Mohamed Mediouni wrote:
>>> Booting macOS Tahoe.
>>> There in the series to show that's all it takes, but not
>>> mergable as is. Testing this requires SIP to be disabled
>>> and AMFI to be bypassed to be able to launch the executable.
>>
>>
>> This is interesting. Do you have any idea what is the private ISA?
>>
>> Regards,
>> Akihiko Odaki
>
> Hello,
>
> For the macOS vmapple target:
>
> Apple PAC is paravirtualised and not trappable by the VMM without
> patching the “hvc #0” to something else.
>
> That’s the only private ISA bit being used there needed for boot.
>
> The documentation for those HVCs:
> https://github.com/matteyeux/darwin-xnu/blob/master/doc/vmapple_pac.md
>
> Apple briefly pushed that there, and open-source XNU has that code present.
>
> When private ISA is disabled, instead of the VMM being able to process those
> HVCs, they return an error code and the guest dutifully goes into a infinite
> loop.
>
> For the vresearch1 target used for PCC VRE and iOS:
>
> Bunch of private ISA used there, including GXF. Private ISA level 3 isn’t
> enough to boot those, it wants private ISA level 4.
It’s fascinating to learn about these Apple-specifics. The insight
regarding the GXF requirement for PCC VRE and iOS is also very
intriguing. Thanks for sharing the information.
Regards,
Akihiko Odaki
next prev parent reply other threads:[~2026-03-25 12:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 20:48 [RFC PATCH v7 0/7] vmapple: making it work on the latest macOS host releases Mohamed Mediouni
2026-03-24 20:48 ` [RFC PATCH v7 1/7] vmapple: apple-gfx: make it work on the latest macOS release Mohamed Mediouni
2026-03-24 20:48 ` [RFC PATCH v7 2/7] hw/vmapple: aes: convert MAX_LEN to a #define Mohamed Mediouni
2026-03-24 20:48 ` [RFC PATCH v7 3/7] vmapple: declare it as an AArch64-compatible machine Mohamed Mediouni
2026-03-25 9:54 ` Philippe Mathieu-Daudé
2026-03-24 20:48 ` [RFC PATCH v7 4/7] Revert "hw/arm: Do not build VMapple machine by default" Mohamed Mediouni
2026-03-24 20:48 ` [RFC PATCH v7 5/7] vmapple: add gicv2m Mohamed Mediouni
2026-03-24 20:48 ` [RFC PATCH v7 6/7] vmapple, gicv2m: add macOS compat quirk Mohamed Mediouni
2026-03-25 9:56 ` Philippe Mathieu-Daudé
2026-03-24 20:48 ` [RFC PATCH v7 7/7] hvf: do not merge: enable private ISA Mohamed Mediouni
2026-03-25 11:07 ` Akihiko Odaki
2026-03-25 11:21 ` Mohamed Mediouni
2026-03-25 12:20 ` Akihiko Odaki [this message]
2026-03-25 11:11 ` [RFC PATCH v7 0/7] vmapple: making it work on the latest macOS host releases Akihiko Odaki
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=a273d3e3-4fcf-4969-b43c-4dadb94ea2c9@rsg.ci.i.u-tokyo.ac.jp \
--to=odaki@rsg.ci.i.u-tokyo.ac.jp \
--cc=agraf@csgraf.de \
--cc=mads@ynddal.dk \
--cc=mohamed@unpredictable.fr \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=phil@philjordan.eu \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rbolshakov@ddn.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