All of lore.kernel.org
 help / color / mirror / Atom feed
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 08:36:42 +0100	[thread overview]
Message-ID: <51A8530A.5030107@citrix.com> (raw)
In-Reply-To: <1369915037.13087.88.camel@zakaz.uk.xensource.com>

On 05/30/2013 12:57 PM, Ian Campbell wrote:
> On Tue, 2013-05-28 at 15:43 -0400, Ross Philipson wrote:
>> [PATCH (V9) 1/2] xen: events, exposes evtchn_alloc_unbound_domain
>> [PATCH (V9) 2/2] xen: Add V4V implementation
> What is happening on the tools/client side?
I'm not sure what kind of tool you want to see here; the only thing i 
can think of is
a way to manipulate the v4v firewall in dom0.

 From a client side PoV, this is up to the guest kernel to expose the 
capability.

For example on linux, the idea is to exposes it is using a new socket 
family, so that
everything is handled by usual syscalls (socket(2), recvmsg(3), 
sendmsg(3), connect(2), listen(2), ioctl(2), ...), and the userspace 
doens't need any library,
and specially just a trivial change to already written code that use ip 
socket without changing any semantics.

-- 
Vincent

  reply	other threads:[~2013-05-31  7:36 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 [this message]
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
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=51A8530A.5030107@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 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.