From: Linhaifeng <haifeng.lin@huawei.com>
To: qemu-devel@nongnu.org
Cc: jerry.lilijun@huawei.com, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] vhost-user:is miss command VHOST_NET_SET_BACKEND?
Date: Wed, 17 Sep 2014 15:50:41 +0800 [thread overview]
Message-ID: <54193D51.6070503@huawei.com> (raw)
In-Reply-To: <54192136.2010409@huawei.com>
sorry it is not need to add VHOST_NET_SET_BACKEND.I found i can reset in VHOST_GET_VRING_BASE because before the backend cleanup it will send VHOST_GET_VRING_BASE.
On 2014/9/17 13:50, Linhaifeng wrote:
> Hi,
>
> The VHOST_NET_SET_BACKEND could tell the user when the backend is created or destroyed.is usefull for the user but this command is lost in the protocol
>
>
>
>
next prev parent reply other threads:[~2014-09-17 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 5:50 [Qemu-devel] vhost-user:is miss command VHOST_NET_SET_BACKEND? Linhaifeng
2014-09-17 7:50 ` Linhaifeng [this message]
2014-09-17 8:33 ` Michael S. Tsirkin
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=54193D51.6070503@huawei.com \
--to=haifeng.lin@huawei.com \
--cc=jerry.lilijun@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).