From: Juan Quintela <quintela@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
Jens Freimann <jfreimann@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] migration: failover: reset partially_hotplugged
Date: Tue, 29 Jun 2021 19:43:03 +0200 [thread overview]
Message-ID: <87r1gkk1nc.fsf@secure.mitica> (raw)
In-Reply-To: <20210629152937.619193-1-lvivier@redhat.com> (Laurent Vivier's message of "Tue, 29 Jun 2021 17:29:37 +0200")
Laurent Vivier <lvivier@redhat.com> wrote:
> When the card is plugged back, reset the partially_hotplugged flag to false
>
> Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1787194
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
> hw/net/virtio-net.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
> index bd7958b9f0ee..16d20cdee52a 100644
> --- a/hw/net/virtio-net.c
> +++ b/hw/net/virtio-net.c
> @@ -3234,6 +3234,7 @@ static bool failover_replug_primary(VirtIONet *n, DeviceState *dev,
> }
> hotplug_handler_plug(hotplug_ctrl, dev, &err);
> }
> + pdev->partially_hotplugged = false;
>
> out:
> error_propagate(errp, err);
Reviewed-by: Juan Quintela <quintela@redhat.com>
But while we are at this:
- In case hotplug_handler_pre_plug() fails, we don't reset it.
No, I have no clue what is the right thing to in that error case.
We have already plugged it once, so it should work (famous last
words).
- Independent of this patch, we check if hotplug_ctrl is NULL, but
nothing else on the tree check for that.
Ok, device_set_realize() check it, but nothing else, except network
failover. I can't see how we are going to be able to arrive there and
not having it, though.
Later, Juan.
next prev parent reply other threads:[~2021-06-29 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 15:29 [PATCH] migration: failover: reset partially_hotplugged Laurent Vivier
2021-06-29 17:43 ` Juan Quintela [this message]
2021-07-06 2:52 ` 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=87r1gkk1nc.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=jasowang@redhat.com \
--cc=jfreimann@redhat.com \
--cc=lvivier@redhat.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 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.