|
Hi, We plan to add a new vsock transport based on hypercall (e.g. vmcall on Intel CPUs). It transports AF_VSOCK packets between the guest and host, which is similar to virtio-vsock, vmci-vsock and hyperv-vsock. Compared to the above listed vsock transports which are designed for high performance, the main advantages of hypercall-vsock are:
1)
It is VMM agnostic. For example, one guest working on hypercall-vsock can run on either KVM, Hyperv, or VMware.
2)
It is simpler. It doesn’t rely on any complex bus enumeration (e.g. virtio-pci based vsock device may need the whole implementation of PCI). An example usage is the communication between MigTD and host (Page 8 at https://static.sched.com/hosted_files/kvmforum2021/ef/TDX%20Live%20Migration_Wei%20Wang.pdf). MigTD communicates to host to assist the migration of the target (user) TD. MigTD is part of the TCB, so its implementation is expected to be as simple as possible (e.g. bare mental implementation without OS, no PCI driver support). Looking forward to your feedbacks. Thanks, Wei |
_______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
