From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-trivial@nongnu.org, Jason Wang <jasowang@redhat.com>,
quintela@redhat.com, Michael Tokarev <mjt@tls.msk.ru>,
Laurent Vivier <laurent@vivier.eu>,
zhengxiang9@huawei.com, jfreimann@redhat.com
Subject: [PATCH v3 0/4] failover: trivial cleanup and fix
Date: Fri, 12 Feb 2021 14:52:46 +0100 [thread overview]
Message-ID: <20210212135250.2738750-1-lvivier@redhat.com> (raw)
The first patch removes a duplicate assignment to
allow_unplug_during_migration, and simplify the code.
The second patch fixes a dangling object in failover_add_primary()
that prevents to cleanup the internal structure after the object has
been unplugged.
v2: add PATCH 3
Report a warning if the failover device is not found
v4: add PATCH 4
Fix a problem in pcie slot link status that makes the kernel
to unplug the card while the virtio-net driver hotplugs it.
Laurent Vivier (4):
pci: cleanup failover sanity check
virtio-net: add missing object_unref()
failover: really display a warning when the primary device is not
found
pcie: don't set link state active if the slot is empty
hw/net/virtio-net.c | 18 +++++++++---------
hw/pci/pci.c | 6 ++----
hw/pci/pcie.c | 19 +++++++++----------
3 files changed, 20 insertions(+), 23 deletions(-)
--
2.29.2
next reply other threads:[~2021-02-12 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 13:52 Laurent Vivier [this message]
2021-02-12 13:52 ` [PATCH v3 1/4] pci: cleanup failover sanity check Laurent Vivier
2021-02-12 14:18 ` Laurent Vivier
2021-02-12 13:52 ` [PATCH v3 2/4] virtio-net: add missing object_unref() Laurent Vivier
2021-02-12 14:18 ` Laurent Vivier
2021-02-12 13:52 ` [PATCH v3 3/4] failover: really display a warning when the primary device is not found Laurent Vivier
2021-02-12 14:40 ` Jens Freimann
2021-02-12 13:52 ` [PATCH v3 4/4] pcie: don't set link state active if the slot is empty Laurent Vivier
2021-02-19 10:10 ` Laurent Vivier
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=20210212135250.2738750-1-lvivier@redhat.com \
--to=lvivier@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jasowang@redhat.com \
--cc=jfreimann@redhat.com \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhengxiang9@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 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).