From: Andy King <acking@vmware.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Cc: gregkh@linuxfoundation.org, davem@davemloft.net,
pv-drivers@vmware.com, kraxel@redhat.com,
Andy King <acking@vmware.com>
Subject: [PATCH 0/1] VM Sockets for Linux upstreaming
Date: Wed, 6 Feb 2013 16:23:55 -0800 [thread overview]
Message-ID: <1360196636-9357-1-git-send-email-acking@vmware.com> (raw)
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[1] 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
hypervisor-neutral.
[1] If Gerd tries it and determines this to be false (still), I'll ship him
a keg of beer.
Andy King (1):
VSOCK: Introduce VM Sockets
include/linux/socket.h | 4 +-
include/uapi/linux/vm_sockets.h | 171 ++
net/Kconfig | 1 +
net/Makefile | 1 +
net/vmw_vsock/Kconfig | 28 +
net/vmw_vsock/Makefile | 7 +
net/vmw_vsock/af_vsock.c | 2015 ++++++++++++++++++++++++
net/vmw_vsock/af_vsock.h | 175 +++
net/vmw_vsock/vmci_transport.c | 2157 ++++++++++++++++++++++++++
net/vmw_vsock/vmci_transport.h | 139 ++
net/vmw_vsock/vmci_transport_notify.c | 680 ++++++++
net/vmw_vsock/vmci_transport_notify.h | 83 +
net/vmw_vsock/vmci_transport_notify_qstate.c | 438 ++++++
net/vmw_vsock/vsock_addr.c | 86 +
net/vmw_vsock/vsock_addr.h | 32 +
net/vmw_vsock/vsock_version.h | 22 +
16 files changed, 6038 insertions(+), 1 deletions(-)
create mode 100644 include/uapi/linux/vm_sockets.h
create mode 100644 net/vmw_vsock/Kconfig
create mode 100644 net/vmw_vsock/Makefile
create mode 100644 net/vmw_vsock/af_vsock.c
create mode 100644 net/vmw_vsock/af_vsock.h
create mode 100644 net/vmw_vsock/vmci_transport.c
create mode 100644 net/vmw_vsock/vmci_transport.h
create mode 100644 net/vmw_vsock/vmci_transport_notify.c
create mode 100644 net/vmw_vsock/vmci_transport_notify.h
create mode 100644 net/vmw_vsock/vmci_transport_notify_qstate.c
create mode 100644 net/vmw_vsock/vsock_addr.c
create mode 100644 net/vmw_vsock/vsock_addr.h
create mode 100644 net/vmw_vsock/vsock_version.h
--
1.7.4.1
next reply other threads:[~2013-02-07 0:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 0:23 Andy King [this message]
2013-02-07 0:23 ` [PATCH 1/1] VSOCK: Introduce VM Sockets Andy King
2013-02-11 14:22 ` Gerd Hoffmann
2013-02-12 15:21 ` Andy King
2013-02-13 3:21 ` [Pv-drivers] " Andy King
2013-02-13 11:06 ` Gerd Hoffmann
2013-02-14 3:20 ` Andy King
2013-02-14 9:28 ` Gerd Hoffmann
2013-02-12 10:58 ` Gerd Hoffmann
2013-02-13 3:23 ` Andy King
2013-02-13 12:44 ` Gerd Hoffmann
2013-02-14 3:07 ` Andy King
2013-02-18 16:56 ` Andy King
2013-02-14 11:05 ` Gerd Hoffmann
2013-02-18 17:07 ` Andy King
2013-02-19 8:45 ` Gerd Hoffmann
2013-02-14 20:18 ` Sasha Levin
2013-02-18 17:09 ` Andy King
2013-02-15 10:32 ` Gerd Hoffmann
2013-02-09 1:20 ` [Pv-drivers] [PATCH 0/1] VM Sockets for Linux upstreaming Dmitry Torokhov
2013-02-09 2:59 ` David Miller
2013-02-11 1:10 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2013-02-04 23:26 Andy King
2013-02-05 16:41 ` Gerd Hoffmann
2013-02-05 17:02 ` Andy King
2013-01-25 17:37 acking
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1360196636-9357-1-git-send-email-acking@vmware.com \
--to=acking@vmware.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).