From: "Michael S. Tsirkin" <mst@redhat.com>
To: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Cc: Damjan Marion <damarion@cisco.com>,
jerry.lilijun@huawei.com, qemu-devel <qemu-devel@nongnu.org>,
Daniel Raho <s.raho@virtualopensystems.com>,
Paolo Bonzini <pbonzini@redhat.com>,
VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
linhafieng <haifeng.lin@huawei.com>
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
Date: Tue, 9 Sep 2014 23:40:51 +0300 [thread overview]
Message-ID: <20140909204051.GA15637@redhat.com> (raw)
In-Reply-To: <CADDJ2=MQRz6pKC_FU5Vs5Zr09473wMevMjHRgEYgV0QM6cSNkQ@mail.gmail.com>
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
next prev parent reply other threads:[~2014-09-09 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5406B47B.7070006@huawei.com>
[not found] ` <20140903070831.GB5449@redhat.com>
2014-09-09 11:45 ` [Qemu-devel] the userspace process vapp mmap filed // [PULL 13/37] vhost-user: fix regions provied with VHOST_USER_SET_MEM_TABLE message linhafieng
2014-09-09 12:28 ` [Qemu-devel] Fwd: " linhafieng
2014-09-09 17:54 ` [Qemu-devel] " Nikolay Nikolaev
2014-09-09 20:40 ` Michael S. Tsirkin [this message]
2014-09-10 3:00 ` Linhaifeng
2014-09-10 11:01 ` Nikolay Nikolaev
[not found] <540FDE71.5090409@huawei.com>
2014-09-10 5:29 ` Linhaifeng
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=20140909204051.GA15637@redhat.com \
--to=mst@redhat.com \
--cc=damarion@cisco.com \
--cc=haifeng.lin@huawei.com \
--cc=jerry.lilijun@huawei.com \
--cc=n.nikolaev@virtualopensystems.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=s.raho@virtualopensystems.com \
--cc=tech@virtualopensystems.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).