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 10:26:33 +0100 [thread overview]
Message-ID: <51A86CC9.1080704@citrix.com> (raw)
In-Reply-To: <1369990887.5199.37.camel@zakaz.uk.xensource.com>
On 05/31/2013 10:01 AM, Ian Campbell wrote:
> I think we need to see and agree on both the client and hypervisor side
> before either can be committed, since review on either could cause ABI
> changes.
Yes, of course. Once some more code is ready, but as of now, we still
need review and comments on
the hypervisor side to make sure the hypervisor part itself is ready
(soundness,design,security,etc).
I want to note however that the v4v capability provided is modeled like
a simplified "network" stack,
so that the design is suppose to stand by itself without any client code.
> What is your upgrade plan for libvchan users? Is it to add vsock support
> to vchan?
I'm not aware of such a plan, nor i'm aware of libvchan or what it
does/doesn't provides in the first place.
If that make sense, then a plan could be devised.
--
Vincent
next prev parent reply other threads:[~2013-05-31 9:26 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
2013-05-31 9:01 ` Ian Campbell
2013-05-31 9:26 ` Vincent Hanquez [this message]
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=51A86CC9.1080704@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).