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 09:56:22 +0100 Message-ID: <51A865B6.1020602@citrix.com> References: <1369770211-4509-1-git-send-email-ross.philipson@citrix.com> <1369915037.13087.88.camel@zakaz.uk.xensource.com> <51A8530A.5030107@citrix.com> <1369986602.5199.7.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: <1369986602.5199.7.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/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