netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy King <acking@vmware.com>
To: David Miller <davem@davemloft.net>
Cc: pv-drivers@vmware.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	gregkh@linuxfoundation.org, georgezhang@vmware.com
Subject: Re: [Pv-drivers] [PATCH 0/6] VSOCK for Linux upstreaming
Date: Mon, 5 Nov 2012 10:19:52 -0800 (PST)	[thread overview]
Message-ID: <783561822.12637564.1352139592543.JavaMail.root@vmware.com> (raw)
In-Reply-To: <20121105.130917.2098838777626057548.davem@davemloft.net>

Hi David,

> The big and only question is whether anyone can actually use any of
> this stuff without your proprietary bits?

Do you mean the VMCI calls?  The VMCI driver is in the process of being
upstreamed into the drivers/misc tree.  Greg (cc'd on these patches) is
actively reviewing that code and we are addressing feedback.

Also, there was some interest from RedHat into using vSockets as a unified
interface, routed over a hypervisor-specific transport (virtio or
otherwise, although for now VMCI is the only one implemented).

Thanks!
- Andy

  parent reply	other threads:[~2012-11-05 18:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 18:00 [PATCH 0/6] VSOCK for Linux upstreaming George Zhang
2012-11-05 18:00 ` [PATCH 1/6] VSOCK: vsock protocol implementation George Zhang
2012-11-06  9:10   ` Stephen Hemminger
2012-11-06 14:31     ` [Pv-drivers] " Andy King
2012-11-05 18:01 ` [PATCH 2/6] VSOCK: vsock address implementaion George Zhang
2012-11-05 18:01 ` [PATCH 3/6] VSOCK: notification implementation George Zhang
2012-11-05 18:01 ` [PATCH 4/6] VSOCK: statistics implementation George Zhang
2012-11-05 18:01 ` [PATCH 5/6] VSOCK: utility functions George Zhang
2012-11-05 18:01 ` [PATCH 6/6] VSOCK: header and config files George Zhang
2012-11-05 18:09 ` [PATCH 0/6] VSOCK for Linux upstreaming David Miller
2012-11-05 18:10   ` David Miller
2012-11-05 18:24     ` George Zhang
2012-11-05 18:19   ` Andy King [this message]
2012-11-07  6:58     ` [Pv-drivers] " Gerd Hoffmann
2012-11-08 15:47       ` Andy King
2012-11-15 21:32       ` Anthony Liguori
2012-11-19  9:59         ` Benjamin Herrenschmidt
2012-12-06 15:28         ` Andy King
2012-11-05 18:23 ` Sasha Levin
2012-11-05 18:32   ` George Zhang
2012-11-11 21:59     ` Sasha Levin
2012-11-14 16:42       ` [Pv-drivers] " Andy King
2012-11-06  9:00 ` Stephen Hemminger
2012-11-06  9:06   ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2013-01-08 23:59 George Zhang
2013-01-09  0:21 ` Greg KH
2013-01-09  1:30   ` David Miller
2013-01-09  1:41     ` [Pv-drivers] " Dmitry Torokhov
2013-01-09  1:46       ` David Miller
2013-01-09  2:22         ` Dmitry Torokhov
2013-01-09  8:10           ` Gerd Hoffmann
2013-01-10  2:42             ` Andy King
2013-01-25 21:33               ` Andy King
2013-02-05  4:42         ` Andy King

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=783561822.12637564.1352139592543.JavaMail.root@vmware.com \
    --to=acking@vmware.com \
    --cc=davem@davemloft.net \
    --cc=georgezhang@vmware.com \
    --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 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).