From: Jason Wang <jasowang@redhat.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: zhangjie14@huawei.com, QEMU Developers <qemu-devel@nongnu.org>,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] vhost_net: start/stop guest notifiers properly
Date: Tue, 19 Aug 2014 10:48:17 +0800 [thread overview]
Message-ID: <53F2BAF1.7050101@redhat.com> (raw)
In-Reply-To: <CAJ75kXaXvfq78PaccDVo2bA4k5f7G7rUP=rrXjj=TpgJyL+eEQ@mail.gmail.com>
On 08/18/2014 09:20 PM, William Dauchy wrote:
> On Mon, Aug 18, 2014 at 11:51 AM, Jason Wang <jasowang@redhat.com> wrote:
>> err:
>> @@ -254,16 +254,16 @@ void vhost_net_stop(VirtIODevice *dev, NetClientState *ncs,
>> VirtioBusClass *k = VIRTIO_BUS_GET_CLASS(vbus);
>> int i, r;
>>
>> + for (i = 0; i < total_queues; i++) {
>> + vhost_net_stop_one(tap_get_vhost_net(ncs[i].peer), dev);
>> + }
>> +
>> r = k->set_guest_notifiers(qbus->parent, total_queues * 2, false);
>> if (r < 0) {
>> fprintf(stderr, "vhost guest notifier cleanup failed: %d\n", r);
>> fflush(stderr);
>> }
>> assert(r >= 0);
>> -
>> - for (i = 0; i < total_queues; i++) {
>> - vhost_net_stop_one(tap_get_vhost_net(ncs[i].peer), dev);
>> - }
>> }
> since
> ed8b4af Refactor virtio-net to use generic get_vhost_net
> get_vhost_net is used instead of tap_get_vhost_net
>
> Could you rebase your patch to facilitate tests or is it intentional?
Not intentional, my tree is out of date. I will rebase the patch.
Thanks for pointing this out.
>
> Thanks,
next prev parent reply other threads:[~2014-08-19 2:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 9:51 [Qemu-devel] [PATCH] vhost_net: start/stop guest notifiers properly Jason Wang
2014-08-18 12:11 ` Zhangjie (HZ)
2014-08-19 2:46 ` Jason Wang
2014-08-18 13:20 ` William Dauchy
2014-08-19 2:48 ` Jason Wang [this message]
2014-08-18 19:53 ` Michael S. Tsirkin
2014-08-19 2:49 ` Jason Wang
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=53F2BAF1.7050101@redhat.com \
--to=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wdauchy@gmail.com \
--cc=zhangjie14@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.