From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58374) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XRaTP-0004jo-Ui for qemu-devel@nongnu.org; Wed, 10 Sep 2014 01:29:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XRaTJ-0002Fx-Q3 for qemu-devel@nongnu.org; Wed, 10 Sep 2014 01:29:43 -0400 Received: from szxga01-in.huawei.com ([119.145.14.64]:27783) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XRaTH-0001y3-6q for qemu-devel@nongnu.org; Wed, 10 Sep 2014 01:29:37 -0400 Message-ID: <540FE19D.5090004@huawei.com> Date: Wed, 10 Sep 2014 13:29:01 +0800 From: Linhaifeng MIME-Version: 1.0 References: <540FDE71.5090409@huawei.com> In-Reply-To: <540FDE71.5090409@huawei.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit 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: "Michael S. Tsirkin" Cc: damarion@cisco.com, jerry.lilijun@huawei.com, n.nikolaev@virtualopensystems.com, qemu-devel@nongnu.org, s.raho@virtualopensystems.com, pbonzini@redhat.com, tech@virtualopensystems.com > From: Michael S. Tsirkin [mailto:mst@redhat.com] > Sent: Wednesday, September 10, 2014 4:41 AM > To: Nikolay Nikolaev > Cc: Linhaifeng; Daniel Raho; qemu-devel; Lilijun (Jerry); Paolo Bonzini; Damjan Marion; VirtualOpenSystems Technical Team > Subject: Re: Re: the userspace process vapp mmap filed //[Qemu-devel] [PULL 13/37] vhost-user: fix regions provied with VHOST_USER_SET_MEM_TABLE message > > 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. > > > I agree with you. I want to ask how to use vhost-user and who will supply and maintence vhost-user.