From: Vincent Hanquez <vincent.hanquez@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ross Philipson <ross.philipson@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH (V9) 0/2] Add V4V to Xen
Date: Fri, 31 May 2013 09:56:22 +0100 [thread overview]
Message-ID: <51A865B6.1020602@citrix.com> (raw)
In-Reply-To: <1369986602.5199.7.camel@zakaz.uk.xensource.com>
On 05/31/2013 08:50 AM, Ian Campbell wrote:
> So where is this code? Has it been posted upstream? Is anyone working on
> getting it in a state such that it acceptable upstream? Would it even be
> acceptable to upstream?
yes, we're in the process to do so.
we're currently re-writing our current driver to use vmware's vsocket,
which is upstream and also has been split up into generic hypervisor
agnostic part (net/vmw_vsock/af_vsock.c) for other hypervisor to use.
As such, it's quite likely it will be acceptable upstream, as we would
fill the xen part for this new linux "standard". This of course would
depends on the xen part being in place too.
--
Vincent
next prev parent reply other threads:[~2013-05-31 8:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 19:43 [PATCH (V9) 0/2] Add V4V to Xen Ross Philipson
2013-05-28 19:43 ` [PATCH (V9) 1/2] xen: events, exposes evtchn_alloc_unbound_domain Ross Philipson
2013-05-28 19:43 ` [PATCH (V9) 2/2] xen: Add V4V implementation Ross Philipson
2013-05-29 0:43 ` Matt Wilson
2013-05-29 19:28 ` Ross Philipson
2013-05-29 8:34 ` Jan Beulich
2013-05-29 19:26 ` Ross Philipson
2013-05-30 5:16 ` Jan Beulich
2013-05-29 9:56 ` Vincent Hanquez
2013-05-30 16:20 ` Tim Deegan
2013-06-04 18:01 ` Ross Philipson
2013-06-10 15:06 ` David Vrabel
2013-05-30 11:57 ` [PATCH (V9) 0/2] Add V4V to Xen Ian Campbell
2013-05-31 7:36 ` Vincent Hanquez
2013-05-31 7:50 ` Ian Campbell
2013-05-31 8:56 ` Vincent Hanquez [this message]
2013-05-31 9:01 ` Ian Campbell
2013-05-31 9:26 ` Vincent Hanquez
2013-05-31 16:29 ` Ross Philipson
2013-05-31 16:38 ` Ian Campbell
2013-05-30 12:07 ` Ian Campbell
2013-05-30 16:08 ` David Vrabel
2013-05-31 7:25 ` Vincent Hanquez
2013-05-31 10:21 ` David Vrabel
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=51A865B6.1020602@citrix.com \
--to=vincent.hanquez@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=ross.philipson@citrix.com \
--cc=xen-devel@lists.xen.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).