Upstream would accept a patchset that exposed an independent Gunyah-specific UAPI (why not the same one as downstream — crosvm already supports that) instead of pretending to be KVM (it's not a "port", you can't port a hypervisor to a hypervisor).
KVM is available on current compute platforms (laptops) if you escape to EL2 via slbounce; and on Glymur (X2E) it will be available by default (yay!).
That's not how operating systems work. KVM is both an interface and a hypervisor. Just as we have different hypervisor implementations for amd, intel, arm and others all abstracted behind the same KVM interface, there is no reason the same can't be done for Gunyah. Userspace does not have to know anything about that. KVM already supports svm and vmx for amd and intel on x86. Why is something similar can't be done for Arm? Plus now there is pKVM.
I just don't understand this argument of a separate interface. The only reason you want to do that is to decouple from the KVM community, but that introduces a shit tone of duplicated effort and needless fragmentation to the virtualisation software ecosystem hindering your users from enjoying the existing upstream tools they already know about. In other terms, vendor locking and shitty downstream experience.
X1E laptops have fully working DisplayPort+USB3+USB2+PD over USB-C unlike Asahi Macbooks :p There really aren't that many gaps in X1E laptop support left.
EL2 is coming by default on Glymur (X2E) (yaaaay), can be enabled in config on some IoT platforms, and can be booted into via Secure Launch on previous compute platforms (Hamoa/Purwa aka X1E/X1P, SC8280XP), search for slbounce.
On phone platforms.. probably not? Or Android might want it for pKVM..
From a quick look, the patch doesn't seem to contain references to Metal, but just a lot of random updates—backports from upstream Wine to the CrossOver thing?—including an AMD ADL implementation that is clearly for Linux (using /sys/class/… stuff). Maybe the whole toolkit is… literally just CrossOver?
Nope. The Game Porting Toolkit itself contains a large `D3DMetal` framework that directly translates Direct3D calls into Metal. The Homebrew repo is only part of the toolkit. To actually use it, you have to move the Direct3D -> Metal translation layer into installed Homebrew prefix. From Apple's README:
The graphics bridge libraries need to be placed inside your Wine prefix in order to finalize your game evaluation environment. These instructions assume you have mounted the Game Porting Toolkit at /Volumes/Game Porting Toolkit-1.0.
• Copy the Game Porting Toolkit library directory into Wine’s library directory.
Seeing "Sizzle" in that profile made me feel shocked. Uhhh Wikipedia actually still uses an ancient build of jQuery that does not take advantage of native querySelector at all?!?
No, jQuery falls back to Sizzle when a selector is not supported by native querySelector, either due to using jQuery-specific extensions, or due to lacking browser support.
