Hector Martin

i think the extra latency is low cost enough to not really matter and the advantages of not having to port OSes to the oddball platform are worth the cost

Sure, if it works and doesn't end up being a user experience compromise down the line, that's fine.

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).

pongoOS is wholly developed by the checkra1n team without outside contributions as of today, we currently license it under MIT, but we'll be able to add a dual-license if necessary.

Yeah, there are a few approaches to merging this kind of code, but if it was MIT to begin with it's unlikely to be a problem. Mainly, someone needs to put a face (and real name) on it once it gets upstreamed, Linux doesn't take anonymous contributions.

we don’t plan on having pongo/HV layer upstreamed into linux, it’s akin to a second-stage (post iBoot) bootloader+thin hv. should probably be separate to linux itself