Re: [PATCH 0/1] VM Sockets for Linux upstreaming
From: David Miller
Date: Sun Feb 10 2013 - 20:10:55 EST
From: Andy King <acking@xxxxxxxxxx>
Date: Wed, 6 Feb 2013 16:23:55 -0800
> In an effort to improve the out-of-the-box experience with Linux kernels for
> VMware users, VMware is working on readying the VM Sockets (VSOCK, formerly
> VMCI Sockets) (vsock) kernel module for inclusion in the Linux kernel. The
> purpose of this post is to acquire feedback on the vsock kernel module.
> Unlike previous submissions, where the new socket family was entirely reliant
> on VMware's VMCI PCI device (and thus VMware's hypervisor), VM Sockets is now
> completely separated out into two parts, each in its own module:
> o Core socket code, which is transport-neutral and invokes transport
> callbacks to communicate with the hypervisor. This is vsock.ko.
> o A VMCI transport, which communicates over VMCI with the VMware hypervisor.
> This is vmw_vsock_vmci_transport.ko, and it registers with the core module
> as a transport.
> This should provide a path to introducing additional transports, for example
> virtio, with the ultimate goal being to make this new socket family
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/