All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Marcel Apfelbaum <marcel@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Anthony Perard <anthony.perard@citrix.com>,
	David Hildenbrand <david@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	Bharata B Rao <bharata@linux.vnet.ibm.com>,
	Amit Shah <amit@kernel.org>
Subject: Re: [Qemu-devel] [PATCH v2] qdev: Mark devices as non-hotpluggable by default
Date: Mon, 25 Sep 2017 10:31:53 -0300	[thread overview]
Message-ID: <20170925133153.GZ3030@localhost.localdomain> (raw)
In-Reply-To: <20170925135316.74fed6da.cohuck@redhat.com>

On Mon, Sep 25, 2017 at 01:53:16PM +0200, Cornelia Huck wrote:
> On Fri, 22 Sep 2017 11:16:34 +0200
> Thomas Huth <thuth@redhat.com> wrote:
> 
> > Historically we've marked all devices as hotpluggable by default. However,
> > most devices are not hotpluggable, and you also need a HotplugHandler to
> > support these devices. So if the user tries to "device_add" or "device_del"
> > such a non-hotpluggable device during runtime, either nothing really usable
> > happens, or QEMU even crashes/aborts unexpectedly (see for example commit
> > 84ebd3e8c7d4fe955b - "Mark diag288 watchdog as non-hotpluggable").
> > So let's change this dangerous default behaviour and mark the devices as
> > non-hotpluggable by default. Certain parent devices classes which are known
> > as hotpluggable (e.g. PCI, USB, etc.) are marked with "hotpluggable = true",
> > so that devices that are derived from these classes continue to work as
> > expected.
> > 
> > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > ---
> >  v2: Add missing devices and dropped "RFC" status. See Eduardo's reply on
> >  the previous version of this patch for the rationale which devices need
> >  to be hotpluggable:
> >  https://lists.gnu.org/archive/html/qemu-devel/2017-09/msg06128.html
> > 
> >  hw/char/virtio-serial-bus.c   |  1 +
> >  hw/core/qdev.c                | 10 ++++------
> >  hw/mem/nvdimm.c               |  3 +++
> >  hw/mem/pc-dimm.c              |  1 +
> >  hw/pci/pci.c                  |  1 +
> >  hw/ppc/spapr_cpu_core.c       |  1 +
> >  hw/s390x/ccw-device.c         |  1 +
> >  hw/scsi/scsi-bus.c            |  1 +
> >  hw/usb/bus.c                  |  1 +
> >  hw/usb/dev-smartcard-reader.c |  1 +
> >  hw/xen/xen_backend.c          |  1 +
> >  target/i386/cpu.c             |  4 ++--
> >  target/s390x/cpu.c            |  1 +
> >  13 files changed, 19 insertions(+), 8 deletions(-)
> 
> Hm, this seems to break hotplug of virtio devices:
> 
> (qemu) device_add virtio-net-pci,id=xxx
> Device 'virtio-net-device' does not support hotplugging
> 
> (qemu) device_add virtio-net-ccw,id=yyy
> Device 'virtio-net-device' does not support hotplugging
> 
> We probably need to enable hotplug for virtio devices as well?

I've seen a similar case broken by "[PATCH] hw/core/qdev: Do not
allow hot-plugging without hotplug controller", because we're
blocking creation of devices created internally by other devices,
not just the ones created by device_add.  I need to find the
exact reproducer again.

It would probably simplify things if we move the check for
DeviceClass::hotpluggable to qmp_device_add(), instead of
device_set_realized().

-- 
Eduardo

  reply	other threads:[~2017-09-25 13:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22  9:16 [Qemu-devel] [PATCH v2] qdev: Mark devices as non-hotpluggable by default Thomas Huth
2017-09-22 10:13 ` David Gibson
2017-09-25 10:13 ` Marcel Apfelbaum
2017-09-25 11:53 ` Cornelia Huck
2017-09-25 13:31   ` Eduardo Habkost [this message]
2017-09-25 13:46     ` Igor Mammedov
2017-09-25 14:34       ` Eduardo Habkost
2017-09-25 15:19         ` Thomas Huth
2017-09-25 15:26           ` Peter Maydell
2017-09-25 17:42             ` Thomas Huth
2017-09-25 17:45               ` Peter Maydell
2017-09-25 17:51                 ` Eduardo Habkost
2017-09-25 18:02                   ` Peter Maydell
2017-09-25 18:20                     ` Eduardo Habkost
2017-09-25 18:46                       ` Peter Maydell
2017-09-25 17:59               ` Eduardo Habkost
2017-09-25 18:05                 ` Peter Maydell
2017-09-25 18:09                   ` Eduardo Habkost
2017-09-26  2:59                   ` Eduardo Habkost
2017-09-26  3:29                     ` Thomas Huth
2017-09-26 16:11                     ` Peter Maydell
2017-09-26 17:27                 ` Thomas Huth
2017-09-26 18:00                   ` Peter Maydell
2017-09-25 17:48             ` Eduardo Habkost
2017-09-26  5:26 ` Bharata B Rao
2017-09-26 10:20   ` Thomas Huth

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=20170925133153.GZ3030@localhost.localdomain \
    --to=ehabkost@redhat.com \
    --cc=amit@kernel.org \
    --cc=anthony.perard@citrix.com \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=david@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.org \
    --cc=thuth@redhat.com \
    --cc=xiaoguangrong.eric@gmail.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 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.