From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Hanquez Subject: Re: [PATCH (V9) 0/2] Add V4V to Xen Date: Fri, 31 May 2013 08:36:42 +0100 Message-ID: <51A8530A.5030107@citrix.com> References: <1369770211-4509-1-git-send-email-ross.philipson@citrix.com> <1369915037.13087.88.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1369915037.13087.88.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Ross Philipson , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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