From: acking@vmware.com
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Cc: pv-drivers@vmware.com, gregkh@linuxfoundation.org,
acking@vmware.com, davem@davemloft.net
Subject: [PATCH 0/1] VM Sockets for Linux upstreaming
Date: Fri, 25 Jan 2013 09:37:49 -0800 [thread overview]
Message-ID: <1359135470-30677-1-git-send-email-acking@vmware.com> (raw)
From: Andy King <acking@vmware.com>
** Introduce VM Sockets ***
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) (vmw_vsock) kernel module for inclusion in the Linux kernel. The
purpose of this post is to acquire feedback on the vmw_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
_mostly_ separated out into two parts:
o Core socket code, which is transport-neutral and invokes transport
callbacks to communicate with the hypervisor.
o A VMCI transport, which communicates over VMCI with the VMware hypervisor.
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.
Andy King (1):
VSOCK: Introduce VM Sockets
include/linux/socket.h | 4 +-
include/uapi/linux/vm_sockets.h | 169 +++
net/Kconfig | 1 +
net/Makefile | 1 +
net/vmw_vsock/Kconfig | 14 +
net/vmw_vsock/Makefile | 4 +
net/vmw_vsock/af_vsock.c | 1983 ++++++++++++++++++++++++++
net/vmw_vsock/af_vsock.h | 256 ++++
net/vmw_vsock/vmci_transport.c | 1863 ++++++++++++++++++++++++
net/vmw_vsock/vmci_transport.h | 90 ++
net/vmw_vsock/vmci_transport_notify.c | 677 +++++++++
net/vmw_vsock/vmci_transport_notify.h | 126 ++
net/vmw_vsock/vmci_transport_notify_qstate.c | 411 ++++++
net/vmw_vsock/vsock_addr.c | 118 ++
net/vmw_vsock/vsock_addr.h | 36 +
net/vmw_vsock/vsock_version.h | 22 +
16 files changed, 5774 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
WARNING: multiple messages have this Message-ID (diff)
From: 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, acking@vmware.com
Subject: [PATCH 0/1] VM Sockets for Linux upstreaming
Date: Fri, 25 Jan 2013 09:37:49 -0800 [thread overview]
Message-ID: <1359135470-30677-1-git-send-email-acking@vmware.com> (raw)
From: Andy King <acking@vmware.com>
** Introduce VM Sockets ***
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) (vmw_vsock) kernel module for inclusion in the Linux kernel. The
purpose of this post is to acquire feedback on the vmw_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
_mostly_ separated out into two parts:
o Core socket code, which is transport-neutral and invokes transport
callbacks to communicate with the hypervisor.
o A VMCI transport, which communicates over VMCI with the VMware hypervisor.
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.
Andy King (1):
VSOCK: Introduce VM Sockets
include/linux/socket.h | 4 +-
include/uapi/linux/vm_sockets.h | 169 +++
net/Kconfig | 1 +
net/Makefile | 1 +
net/vmw_vsock/Kconfig | 14 +
net/vmw_vsock/Makefile | 4 +
net/vmw_vsock/af_vsock.c | 1983 ++++++++++++++++++++++++++
net/vmw_vsock/af_vsock.h | 256 ++++
net/vmw_vsock/vmci_transport.c | 1863 ++++++++++++++++++++++++
net/vmw_vsock/vmci_transport.h | 90 ++
net/vmw_vsock/vmci_transport_notify.c | 677 +++++++++
net/vmw_vsock/vmci_transport_notify.h | 126 ++
net/vmw_vsock/vmci_transport_notify_qstate.c | 411 ++++++
net/vmw_vsock/vsock_addr.c | 118 ++
net/vmw_vsock/vsock_addr.h | 36 +
net/vmw_vsock/vsock_version.h | 22 +
16 files changed, 5774 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-01-25 17:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 17:37 acking [this message]
2013-01-25 17:37 ` [PATCH 0/1] VM Sockets for Linux upstreaming acking
2013-01-25 17:37 ` [PATCH 1/1] VSOCK: Introduce VM Sockets acking
2013-01-25 17:37 ` acking
2013-01-25 23:59 ` Neil Horman
2013-01-26 0:15 ` [Pv-drivers] " Dmitry Torokhov
2013-01-26 0:22 ` Greg KH
2013-01-26 0:22 ` Greg KH
2013-01-26 0:22 ` Greg KH
2013-01-26 18:41 ` Neil Horman
2013-01-26 18:41 ` Neil Horman
2013-01-26 0:15 ` Dmitry Torokhov
2013-01-25 23:59 ` Neil Horman
2013-01-28 12:25 ` Gerd Hoffmann
2013-01-28 12:25 ` Gerd Hoffmann
2013-01-31 22:06 ` Andy King
2013-01-31 22:06 ` Andy King
2013-02-01 8:12 ` Gerd Hoffmann
2013-02-01 8:12 ` Gerd Hoffmann
2013-02-01 8:12 ` Gerd Hoffmann
2013-02-04 23:41 ` Andy King
2013-02-04 23:41 ` Andy King
-- strict thread matches above, loose matches on Subject: below --
2013-02-04 23:26 [PATCH 0/1] VM Sockets for Linux upstreaming Andy King
2013-02-05 16:41 ` Gerd Hoffmann
2013-02-05 16:41 ` Gerd Hoffmann
2013-02-05 17:02 ` Andy King
2013-02-05 17:02 ` Andy King
2013-02-04 23:26 Andy King
2013-02-07 0:23 Andy King
2013-02-07 0:23 Andy King
2013-02-11 1:10 ` David Miller
2013-02-11 1:10 ` David Miller
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=1359135470-30677-1-git-send-email-acking@vmware.com \
--to=acking@vmware.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.