From: Adrian Moreno <amorenoz@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: ddstreet@canonical.com, Pei Zhang <pezhang@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vhost-user: save features if the char dev is closed
Date: Wed, 18 Sep 2019 10:40:40 +0200 [thread overview]
Message-ID: <a9cf2607-9384-ec12-e3d9-86b2aeb69660@redhat.com> (raw)
In-Reply-To: <20190917173941-mutt-send-email-mst@kernel.org>
On 9/17/19 11:40 PM, Michael S. Tsirkin wrote:
> On Tue, Sep 17, 2019 at 09:19:01PM +0200, Adrian Moreno wrote:
>> That way the state can be correctly restored when the device is opened
>> again. This might happen if the backend is restarted.
>>
>> Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1738768
>> Reported-by: Pei Zhang <pezhang@redhat.com>
>> Fixes: 6ab79a20af3a (do not call vhost_net_cleanup() on running net from char user event)
>> Cc: ddstreet@canonical.com
>> Cc: Michael S. Tsirkin <mst@redhat.com>
>>
>> Signed-off-by: Adrian Moreno <amorenoz@redhat.com>
>> ---
>> net/vhost-user.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/net/vhost-user.c b/net/vhost-user.c
>> index 51921de443..acf20cb9e0 100644
>> --- a/net/vhost-user.c
>> +++ b/net/vhost-user.c
>> @@ -235,6 +235,13 @@ static void chr_closed_bh(void *opaque)
>>
>> s = DO_UPCAST(NetVhostUserState, nc, ncs[0]);
>>
>> + if (s->vhost_net) {
>> + uint64_t features = vhost_net_get_acked_features(s->vhost_net);
>> + if (features) {
>> + s->acked_features = features;
>> + }
>
> why does it make sense to check if (features)?
> 0x0 is a valid feature bitmap, isn't it?
You're right. It doesn't.
I'll remove the check.
>
>> + }
>> +
>> qmp_set_link(name, false, &err);
>>
>> qemu_chr_fe_set_handlers(&s->chr, NULL, NULL, net_vhost_user_event,
>> --
>> 2.21.0
Thanks.
prev parent reply other threads:[~2019-09-18 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 19:19 [Qemu-devel] [PATCH] vhost-user: save features if the char dev is closed Adrian Moreno
2019-09-17 21:40 ` Michael S. Tsirkin
2019-09-18 8:40 ` Adrian Moreno [this message]
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=a9cf2607-9384-ec12-e3d9-86b2aeb69660@redhat.com \
--to=amorenoz@redhat.com \
--cc=ddstreet@canonical.com \
--cc=mst@redhat.com \
--cc=pezhang@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).