Demi Marie Obenour

To elaborate: Windows, macOS, iOS, and Android have a system-provided webview, but desktop Linux and embedded systems do not. Embedded devices, obviously, have no webview unless they bring their own....

Wow, this is pretty bad. I can understand that assigning them would break things, but this should not break the whole system!

@dorindabassey How will this compare to the existing virtio-GPU device implemented in crosvm? crosvm already has vhost-user support. Blob objects (needed for Vulkan and native contexts) require non-standard vhost-user messages,...

@alyssais, @QubesOS, and Chrome OS all need each window in the guest to be a separate window on the host. Therefore, they are or will be using Wayland passthrough, rather...

Having the backend do the rendering is highly desirable from a security perspective, as it allows the frontend to be sandboxed. The backend must be quite privileged as it can...

I’m opposed to this position, mostly because I can’t see open operating systems (desktop Linux) ever supporting it.

Yes, they should be marked as `unsafe`, or wrapped in a safe abstraction.

I suspect the hard part will be writing the `// SAFETY` comments at the call sites. I’m not familiar enough with Cloud Hypervisor to do that.

> Hello @DemiMarie, when we last spoke you mentioned that virtiofs was a better choice, rather than the Xen 9pfs protocol specification. Do you have any thoughts on that you...

One feature that may need to be added to Xen is Linux kernel MMU notifier support. This **will** happen because AMD needs it for virtio-GPU native contexts, which they will...