So what do you think? Is this something you'd actually throw money at? If there is enough interest that this might succeed, I'll open up a Patreon. Obviously all development would be public and open source.
Show this thread
-
What made us seriously think about it is that M1 is new enough to have nested virtualisation, so that the thin hypervisor for this can still expose the full CPU feature set to the guest.
Yeah, that's a big one. Though nested virt usually has a nontrivial perf cost, but it depends on the implementation. E.g. what is the cost of the extra pagetable level (which presumably at least can be using very large pages)?
-
-
But anyway, there is always time to ditch the virtualization if it becomes the limiting factor, so I'm not too worried about that. Crossporting drivers back into the kernel is trivial compared to, like, GPU support (assuming the license permits).
-
That one's a big one though, wouldn't want HV dev effort wasted, so you'd want to stick to kernel licensing rules there from day one.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.