From: Cornelia Huck <cohuck@redhat.com>
To: Jens Freimann <jfreimann@redhat.com>
Cc: parav@mellanox.com, mst@redhat.com, aadam@redhat.com,
qemu-devel@nongnu.org, dgilbert@redhat.com,
alex.williamson@redhat.com, laine@redhat.com, ailan@redhat.com,
ehabkost@redhat.com
Subject: Re: [PATCH v3 01/10] qdev/qbus: add hidden device support
Date: Mon, 14 Oct 2019 11:46:22 +0200 [thread overview]
Message-ID: <20191014114622.6dcd9f90.cohuck@redhat.com> (raw)
In-Reply-To: <20191011112015.11785-2-jfreimann@redhat.com>
On Fri, 11 Oct 2019 13:20:06 +0200
Jens Freimann <jfreimann@redhat.com> wrote:
> This adds support for hiding a device to the qbus and qdev APIs. The
> first user of this will be the virtio-net failover feature but the API
> introduced with this patch could be used to implement other features as
> well, for example hiding pci devices when a pci bus is powered off.
>
> qdev_device_add() is modified to check for a net_failover_pair_id
> argument in the option string. A DeviceListener callback
> should_be_hidden() is added. It can be used by a standby device to
> inform qdev that this device should not be added now. The standby device
> handler can store the device options to plug the device in at a later
> point in time.
>
> One reason for hiding the device is that we don't want to expose both
> devices to the guest kernel until the respective virtio feature bit
> VIRTIO_NET_F_STANDBY was negotiated and we know that the devices will be
> handled correctly by the guest.
>
> More information on the kernel feature this is using:
> https://www.kernel.org/doc/html/latest/networking/net_failover.html
>
> An example where the primary device is a vfio-pci device and the standby
> device is a virtio-net device:
>
> A device is hidden when it has an "net_failover_pair_id" option, e.g.
>
> -device virtio-net-pci,...,failover=on,...
> -device vfio-pci,...,net_failover_pair_id=net1,...
>
> Signed-off-by: Jens Freimann <jfreimann@redhat.com>
> ---
> hw/core/qdev.c | 19 +++++++++++++++++++
> include/hw/qdev-core.h | 9 +++++++++
> qdev-monitor.c | 43 ++++++++++++++++++++++++++++++++++++++----
> vl.c | 6 ++++--
> 4 files changed, 71 insertions(+), 6 deletions(-)
>
(...)
> diff --git a/include/hw/qdev-core.h b/include/hw/qdev-core.h
> index aa123f88cb..b61cf82ded 100644
> --- a/include/hw/qdev-core.h
> +++ b/include/hw/qdev-core.h
> @@ -154,6 +154,13 @@ struct DeviceState {
> struct DeviceListener {
> void (*realize)(DeviceListener *listener, DeviceState *dev);
> void (*unrealize)(DeviceListener *listener, DeviceState *dev);
> + /*
> + * This callback is called just upon init of the DeviceState
> + * and can be used by a standby device for informing qdev if this
> + * device should be hidden by checking the device opts
> + */
Maybe tweak this comment a bit:
/*
* This callback is called upon init of the DeviceState and allows to
* inform qdev that a device should be hidden, depending on the device
* opts, for example, to hide a standby device.
*/
This makes it clearer that this interface could be reused for other
purposes.
> + void (*should_be_hidden)(DeviceListener *listener, QemuOpts *device_opts,
> + bool *match_found, bool *res);
> QTAILQ_ENTRY(DeviceListener) link;
> };
>
> @@ -451,4 +458,6 @@ static inline bool qbus_is_hotpluggable(BusState *bus)
> void device_listener_register(DeviceListener *listener);
> void device_listener_unregister(DeviceListener *listener);
>
> +bool qdev_should_hide_device(QemuOpts *opts, Error **errp);
> +
> #endif
> diff --git a/qdev-monitor.c b/qdev-monitor.c
> index 148df9cacf..9fc8331157 100644
> --- a/qdev-monitor.c
> +++ b/qdev-monitor.c
> @@ -32,9 +32,11 @@
> #include "qemu/help_option.h"
> #include "qemu/option.h"
> #include "qemu/qemu-print.h"
> +#include "qemu/option_int.h"
> #include "sysemu/block-backend.h"
> #include "sysemu/sysemu.h"
> #include "migration/misc.h"
> +#include "migration/migration.h"
>
> /*
> * Aliases were a bad idea from the start. Let's keep them
> @@ -562,14 +564,45 @@ void qdev_set_id(DeviceState *dev, const char *id)
> }
> }
>
> +static int is_failover_device(void *opaque, const char *name, const char *value,
> + Error **errp)
> +{
> + if (strcmp(name, "net_failover_pair_id") == 0) {
> + QemuOpts *opts = (QemuOpts *)opaque;
> +
> + if (qdev_should_hide_device(opts, errp) && errp && !*errp) {
> + return 1;
> + } else if (errp && *errp) {
> + return -1;
> + }
> + }
> +
> + return 0;
> +}
> +
> +static bool should_hide_device(QemuOpts *opts, Error **err)
> +{
> + if (qemu_opt_foreach(opts, is_failover_device, opts, err) == 0) {
> + return false;
Maybe turn that check around? I.e. return true if the failover property
is present, else return false. Makes it easier to add checks for other
properties in the future.
> + }
> + return true;
> +}
> +
> DeviceState *qdev_device_add(QemuOpts *opts, Error **errp)
> {
> DeviceClass *dc;
> const char *driver, *path;
> - DeviceState *dev;
> + DeviceState *dev = NULL;
> BusState *bus = NULL;
> Error *err = NULL;
>
> + if (opts && should_hide_device(opts, &err)) {
> + if (err) {
> + goto err_del_dev;
> + }
> + return NULL;
> + }
> +
> driver = qemu_opt_get(opts, "driver");
> if (!driver) {
> error_setg(errp, QERR_MISSING_PARAMETER, "driver");
> @@ -648,8 +681,10 @@ DeviceState *qdev_device_add(QemuOpts *opts, Error **errp)
>
> err_del_dev:
> error_propagate(errp, err);
> - object_unparent(OBJECT(dev));
> - object_unref(OBJECT(dev));
> + if (dev) {
> + object_unparent(OBJECT(dev));
> + object_unref(OBJECT(dev));
> + }
> return NULL;
> }
>
> @@ -818,7 +853,7 @@ void qdev_unplug(DeviceState *dev, Error **errp)
> return;
> }
>
> - if (!migration_is_idle()) {
> + if (!migration_is_idle() && !migration_in_setup(migrate_get_current())) {
Hm, should that hunk go into another patch?
> error_setg(errp, "device_del not allowed while migrating");
> return;
> }
(...)
next prev parent reply other threads:[~2019-10-14 9:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 11:20 [PATCH v3 0/10] add failover feature for assigned network devices Jens Freimann
2019-10-11 11:20 ` [PATCH v3 01/10] qdev/qbus: add hidden device support Jens Freimann
2019-10-14 9:46 ` Cornelia Huck [this message]
2019-10-14 12:02 ` Jens Freimann
2019-10-15 19:19 ` Alex Williamson
2019-10-16 7:04 ` Jens Freimann
2019-10-11 11:20 ` [PATCH v3 02/10] pci: mark devices partially unplugged Jens Freimann
2019-10-16 1:53 ` Alex Williamson
2019-10-11 11:20 ` [PATCH v3 03/10] pci: mark device having guest unplug request pending Jens Freimann
2019-10-11 11:20 ` [PATCH v3 04/10] qapi: add unplug primary event Jens Freimann
2019-10-11 11:20 ` [PATCH v3 05/10] qapi: add failover negotiated event Jens Freimann
2019-10-11 11:20 ` [PATCH v3 06/10] migration: allow unplug during migration for failover devices Jens Freimann
2019-10-11 11:20 ` [PATCH v3 07/10] migration: add new migration state wait-unplug Jens Freimann
2019-10-11 12:57 ` Michael S. Tsirkin
2019-10-11 14:22 ` Jens Freimann
2019-10-11 16:49 ` Dr. David Alan Gilbert
2019-10-11 17:11 ` Dr. David Alan Gilbert
2019-10-15 9:45 ` Jens Freimann
2019-10-15 10:50 ` Dr. David Alan Gilbert
2019-10-16 7:07 ` Jens Freimann
2019-10-11 11:20 ` [PATCH v3 08/10] libqos: tolerate wait-unplug migration state Jens Freimann
2019-10-11 11:20 ` [PATCH v3 09/10] net/virtio: add failover support Jens Freimann
2019-10-11 11:20 ` [PATCH v3 10/10] vfio: unplug failover primary device before migration Jens Freimann
2019-10-14 10:05 ` Cornelia Huck
2019-10-16 1:52 ` Alex Williamson
2019-10-16 20:18 ` Jens Freimann
2019-10-17 0:39 ` Alex Williamson
2019-10-17 7:45 ` Jens Freimann
2019-10-11 14:28 ` [PATCH v3 0/10] add failover feature for assigned network devices Michael S. Tsirkin
2019-10-11 16:04 ` no-reply
2019-10-15 19:03 ` Alex Williamson
2019-10-15 21:17 ` Michael S. Tsirkin
2019-10-17 10:33 ` Jens Freimann
2019-10-17 12:51 ` Alex Williamson
2019-10-17 14:04 ` Jens Freimann
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=20191014114622.6dcd9f90.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=aadam@redhat.com \
--cc=ailan@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jfreimann@redhat.com \
--cc=laine@redhat.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.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).