All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Freimann <jfreimann@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Peter Krempa <pkrempa@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	aadam@redhat.com, QEMU Developers <qemu-devel@nongnu.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Laine Stump <laine@redhat.com>, Amnon Ilan <ailan@redhat.com>,
	parav@mellanox.com
Subject: Re: [PATCH 01/11] qdev/qbus: add hidden device support
Date: Mon, 21 Oct 2019 15:00:33 +0200	[thread overview]
Message-ID: <20191021130033.qx5jy53ir4dllefb@jenstp.localdomain> (raw)
In-Reply-To: <CAFEAcA-wE1vt_dWsa-k+VK8T0YyRKiPhXUYNYdYVk98nekg=zw@mail.gmail.com>

On Mon, Oct 21, 2019 at 01:53:58PM +0100, Peter Maydell wrote:
>On Fri, 18 Oct 2019 at 21:22, 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.
>
>In what sense is a hidden device hidden? Is it hidden from
>the guest (in what way) ? Is it hidden from the QMP/HMP monitor
>commands? Is it hidden from QEMU functions that iterate through
>the qbus, or that walk the QOM tree ? What does a hidden device
>have to do to be successfully hidden ? Is it completely disconnected
>from the rest of the simulation, or does it itself have to avoid
>doing things like asserting IRQ lines ?
>
>Expanding the DeviceClass doc comment might be a good place to answer
>questions like the above and generally describe the 'hidden device'
>mechanism.

ok, I will add to the DeviceClass comment. 

>
>>  };
>>
>> @@ -451,4 +457,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);
>
>New globally visible functions should always have doc-comment
>format documentation comments, please.

Will add this too. Thanks for the review!

regards,
Jens 



  reply	other threads:[~2019-10-21 13:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 20:20 [PATCH v4 0/11] add failover feature for assigned network devices Jens Freimann
2019-10-18 20:20 ` [PATCH 01/11] qdev/qbus: add hidden device support Jens Freimann
2019-10-21 12:44   ` Cornelia Huck
2019-10-21 12:52     ` Jens Freimann
2019-10-21 12:53   ` Peter Maydell
2019-10-21 13:00     ` Jens Freimann [this message]
2019-10-18 20:20 ` [PATCH 02/11] pci: add option for net failover Jens Freimann
2019-10-21 14:58   ` Alex Williamson
2019-10-21 18:45     ` Jens Freimann
2019-10-21 19:01       ` Alex Williamson
2019-10-21 20:28         ` Jens Freimann
2019-10-21 20:48           ` Alex Williamson
2019-10-18 20:20 ` [PATCH 03/11] pci: mark devices partially unplugged Jens Freimann
2019-10-18 20:20 ` [PATCH 04/11] pci: mark device having guest unplug request pending Jens Freimann
2019-10-18 20:20 ` [PATCH 05/11] qapi: add unplug primary event Jens Freimann
2019-10-18 20:28   ` Eric Blake
2019-10-21  7:23     ` Jens Freimann
2019-10-18 20:20 ` [PATCH 06/11] qapi: add failover negotiated event Jens Freimann
2019-10-18 20:20 ` [PATCH 07/11] migration: allow unplug during migration for failover devices Jens Freimann
2019-10-18 20:20 ` [PATCH 08/11] migration: add new migration state wait-unplug Jens Freimann
2019-10-18 20:20 ` [PATCH 09/11] libqos: tolerate wait-unplug migration state Jens Freimann
2019-10-18 20:20 ` [PATCH 10/11] net/virtio: add failover support Jens Freimann
2019-10-18 20:20 ` [PATCH 11/11] vfio: unplug failover primary device before migration Jens Freimann
2019-10-21 13:45   ` Cornelia Huck
2019-10-21 14:09     ` Jens Freimann
2019-10-21 15:19   ` Alex Williamson
2019-10-21 19:16     ` Jens Freimann
2019-10-19 15:12 ` [PATCH v4 0/11] add failover feature for assigned network devices no-reply
2019-10-21  7:30   ` Jens Freimann
2019-10-19 15:15 ` no-reply
2019-10-21 14:18 ` Cornelia Huck

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=20191021130033.qx5jy53ir4dllefb@jenstp.localdomain \
    --to=jfreimann@redhat.com \
    --cc=aadam@redhat.com \
    --cc=ailan@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=laine@redhat.com \
    --cc=mst@redhat.com \
    --cc=parav@mellanox.com \
    --cc=peter.maydell@linaro.org \
    --cc=pkrempa@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.