From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59048) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XRSAf-00050n-9p for qemu-devel@nongnu.org; Tue, 09 Sep 2014 16:37:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XRSAY-0000h4-Vf for qemu-devel@nongnu.org; Tue, 09 Sep 2014 16:37:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:20226) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XRSAY-0000h0-Nl for qemu-devel@nongnu.org; Tue, 09 Sep 2014 16:37:42 -0400 Date: Tue, 9 Sep 2014 23:40:51 +0300 From: "Michael S. Tsirkin" Message-ID: <20140909204051.GA15637@redhat.com> References: <540EE844.8080507@huawei.com> <540EF275.10201@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] the userspace process vapp mmap filed // [PULL 13/37] vhost-user: fix regions provied with VHOST_USER_SET_MEM_TABLE message List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nikolay Nikolaev Cc: Damjan Marion , jerry.lilijun@huawei.com, qemu-devel , Daniel Raho , Paolo Bonzini , VirtualOpenSystems Technical Team , linhafieng On Tue, Sep 09, 2014 at 08:54:08PM +0300, Nikolay Nikolaev wrote: > Hello, > > Vapp is a VOSYS application, currently not meant to be part of QEMU; > as such your proposed patch might not be meaningful if pushed towards > QEMU devel list. > As the current Vapp implementation is not updated > since last March, custom support and any related potential design need > for a software switch implementation can be discussed at a custom > commercial level. > > regards, > Nikolay Nikolaev > Virtual Open Systems I'm not familiar enough with the software itself to comment on the patch. But I don't think yours is a valid answer, and I was the one who asked that the question is sent to the list. I merged the vhost-user protocol so we can support multiple backends. Someone wants to work on another backend, more power to them, Way I read it the question is whether there's a bug in vhost in qemu, and how to use vhost-user, and this seems relevant on our list. -- MST