qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, peter.maydell@linaro.org,
	peter.crosthwaite@xilinx.com, stefanha@redhat.com,
	mst@redhat.com, jan.kiszka@siemens.com, marcel.a@redhat.com,
	qemu-devel@nongnu.org, armbru@redhat.com, blauwirbel@gmail.com,
	alex.williamson@redhat.com, kraxel@redhat.com,
	aliguori@amazon.com, pbonzini@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v5 2/9] qdev: add to BusState "hotplug-handler" link
Date: Tue, 4 Feb 2014 09:43:24 +0100	[thread overview]
Message-ID: <20140204094324.61790520@thinkpad> (raw)
In-Reply-To: <52F000FA.9060408@redhat.com>

On Mon, 03 Feb 2014 13:50:02 -0700
Eric Blake <eblake@redhat.com> wrote:

> On 02/03/2014 01:38 PM, Igor Mammedov wrote:
> 
> >>> +static inline void qbus_set_hotplug_handler(BusState *bus, DeviceState *handler,
> >>> +                                            Error **errp)
> >>> +{
> >>> +    object_property_set_link(OBJECT(bus), OBJECT(handler),
> >>> +                             QDEV_HOTPLUG_HANDLER_PROPERTY, errp);
> >>> +    bus->allow_hotplug = 1;
> >>
> >> Should we convert allow_hotplug to bool over the course of this series?
> > There isn't much point in touching it, since it's going to be removed once
> > all hotplug-able buses are converted to new interface.
> 
> After finishing my read through your series, I noticed that you were
> using allow_hotplug less and less and instead using a new bool in most
> code you added.  Does that just mean your series didn't touch every last
> client of the old interface, and that there still remains code to be
> converted, where this series serves as the example of how?
Yes, beside adding new hotplug mechanism, it converts only PCI hotplug
workflow as example.
Paolo had plans to convert scsi hotplug once this series is in.

> 
> -- 
> Eric Blake   eblake redhat com    +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
> 


-- 
Regards,
  Igor

  reply	other threads:[~2014-02-04  8:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 15:57 [Qemu-devel] [PATCH v5 0/9] Refactor PCI/SHPC/PCIE hotplug to use a more generic hotplug API Igor Mammedov
2014-02-03 15:57 ` [Qemu-devel] [PATCH v5 1/9] define hotplug interface Igor Mammedov
2014-02-03 19:28   ` Eric Blake
2014-02-03 15:57 ` [Qemu-devel] [PATCH v5 2/9] qdev: add to BusState "hotplug-handler" link Igor Mammedov
2014-02-03 19:30   ` Eric Blake
2014-02-03 20:38     ` Igor Mammedov
2014-02-03 20:50       ` Eric Blake
2014-02-04  8:43         ` Igor Mammedov [this message]
2014-02-03 15:57 ` [Qemu-devel] [PATCH v5 3/9] qdev: add "hotpluggable" property to Device Igor Mammedov
2014-02-03 19:31   ` Eric Blake
2014-02-03 15:57 ` [Qemu-devel] [PATCH v5 4/9] hw/acpi: move typeinfo to the file end Igor Mammedov
2014-02-03 19:32   ` Eric Blake
2014-02-03 15:57 ` [Qemu-devel] [PATCH v5 5/9] qdev:pci: refactor PCIDevice to use generic "hotpluggable" property Igor Mammedov
2014-02-03 15:57 ` [Qemu-devel] [PATCH v5 6/9] acpi/piix4pm: convert ACPI PCI hotplug to use hotplug-handler API Igor Mammedov
2014-02-03 19:34   ` Eric Blake
2014-02-03 15:57 ` [Qemu-devel] [PATCH v5 7/9] pci/shpc: convert SHPC " Igor Mammedov
2014-02-03 15:57 ` [Qemu-devel] [PATCH v5 8/9] pci/pcie: convert PCIE " Igor Mammedov
2014-02-03 15:57 ` [Qemu-devel] [PATCH v5 9/9] hw/pci: switch to a generic hotplug handling for PCIDevice Igor Mammedov
2014-02-03 19:37 ` [Qemu-devel] [PATCH v5 0/9] Refactor PCI/SHPC/PCIE hotplug to use a more generic hotplug API Eric Blake
2014-02-03 20:42   ` Igor Mammedov

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=20140204094324.61790520@thinkpad \
    --to=imammedo@redhat.com \
    --cc=afaerber@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=armbru@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=eblake@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).