From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Tina Zhang <tina.zhang@intel.com>,
intel-gvt-dev@lists.freedesktop.org,
Kirti Wankhede <kwankhede@nvidia.com>,
Markus Armbruster <armbru@redhat.com>,
Eric Blake <eblake@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 4/7] qdev: add hotpluggable to DeviceState
Date: Thu, 22 Feb 2018 09:59:17 -0700 [thread overview]
Message-ID: <20180222095917.29eda1d9@w520.home> (raw)
In-Reply-To: <CAFEAcA8_VRML=FopCKdGnrPCyZ9MwKokMj60962=tgCNwNT2oA@mail.gmail.com>
On Thu, 22 Feb 2018 15:46:17 +0000
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 22 February 2018 at 15:37, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > On Mon, Feb 19, 2018 at 12:14:55PM +0100, Gerd Hoffmann wrote:
> >> vfio display support wants disable hotplug for certain devices, because
> >> qemu doesn't support hotplugging display devices and qemu consoles.
> >>
> >> Add a hotpluggable bool to DeviceState, initialize it from
> >> DeviceClass->hotpluggable, update device_get_hotpluggable accordingly.
> >>
> >> Devices can flip the new variable from true to false if needed.
> >
> > Alex wants an ack for this one. Who maintains it these days?
> >
> > MAINTAINERS doesn't list qdev. For QOM which is closest probably
> > Andreas Färber is listed. Havn't seen him on the list for a while
> > though.
> >
> > Ok, lets try some usual suspects...
> > Markus? Eric? Paolo? Peter? Any comments on this one?
>
> What type of device is only sometimes hotpluggable ?
> The commit message says "display devices" and "consoles",
> but I would expect those to both be types of device which
> have a class which is never hotpluggable, so you can mark
> them non-hotpluggable with the existing class flag rather
> than needing a per-instance flag.
With this series, a vfio-pci device optionally supports a display. The
vfio-pci device is hotpluggable, but QEMU display support is not. So
the solution here is to make the vfio-pci device non-hotpluggable only
when it supports and enables a display.
Gerd, is there another solution that the display object is instantiated
separately from the vfio-pci object and the display support in the
vfio-pci device references the display object via an id. Possibly
vfio-pci could remain hotpluggable while the display class device is
not. Potentially one display could be switched between multiple
display capable devices, like an input control button on a monitor,
losing signal if none are connected. Possible? Clearly I have no idea
how display objects actually work in QEMU. Thanks,
Alex
next prev parent reply other threads:[~2018-02-22 16:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 11:14 [Qemu-devel] [PATCH v4 0/7] vfio: add display support Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 1/7] linux-headers: update to 4.16-rc1 Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 2/7] standard-headers: add drm/drm_fourcc.h Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 3/7] ui/pixman: add qemu_drm_format_to_pixman() Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 4/7] qdev: add hotpluggable to DeviceState Gerd Hoffmann
2018-02-22 15:37 ` Gerd Hoffmann
2018-02-22 15:46 ` Peter Maydell
2018-02-22 16:59 ` Alex Williamson [this message]
2018-02-22 17:21 ` Peter Maydell
2018-02-23 3:14 ` Zhenyu Wang
2018-02-23 8:53 ` Gerd Hoffmann
2018-02-23 15:58 ` Alex Williamson
2018-02-26 8:23 ` Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 5/7] vfio/common: cleanup in vfio_region_finalize Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 6/7] vfio/display: core & wireup Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 7/7] vfio/display: adding region support Gerd Hoffmann
2018-02-19 22:16 ` [Qemu-devel] [PATCH v4 0/7] vfio: add display support Alex Williamson
2018-02-20 10:28 ` Gerd Hoffmann
2018-02-20 17:04 ` Gerd Hoffmann
2018-02-22 6:40 ` Zhenyu Wang
2018-02-22 9:30 ` Gerd Hoffmann
2018-02-23 2:42 ` Zhenyu Wang
2018-02-23 7:06 ` Zhang, Tina
2018-02-22 16:28 ` Alex Williamson
2018-02-23 9:05 ` Gerd Hoffmann
2018-02-26 8:35 ` Gerd Hoffmann
2018-02-26 20:59 ` Alex Williamson
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=20180222095917.29eda1d9@w520.home \
--to=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=kwankhede@nvidia.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tina.zhang@intel.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).