From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 2/3] piix: tag as not hotpluggable.
Date: Wed, 5 Jan 2011 21:44:06 +0200 [thread overview]
Message-ID: <20110105194406.GC28688@redhat.com> (raw)
In-Reply-To: <1291123564-3249-3-git-send-email-kraxel@redhat.com>
On Tue, Nov 30, 2010 at 02:26:03PM +0100, Gerd Hoffmann wrote:
> This patch tags all pci devices which belong to the piix3/4 chipsets as
> not hotpluggable (Host bridge, ISA bridge, IDE controller, ACPI bridge).
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> hw/acpi_piix4.c | 2 ++
> hw/ide/piix.c | 2 ++
> hw/piix4.c | 1 +
> hw/piix_pci.c | 2 ++
> 4 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/hw/acpi_piix4.c b/hw/acpi_piix4.c
> index 173d781..273097d 100644
> --- a/hw/acpi_piix4.c
> +++ b/hw/acpi_piix4.c
> @@ -428,6 +428,8 @@ static PCIDeviceInfo piix4_pm_info = {
> .qdev.desc = "PM",
> .qdev.size = sizeof(PIIX4PMState),
> .qdev.vmsd = &vmstate_acpi,
> + .qdev.no_user = 1,
> + .no_hotplug = 1,
> .init = piix4_pm_initfn,
> .config_write = pm_write_config,
> .qdev.props = (Property[]) {
> diff --git a/hw/ide/piix.c b/hw/ide/piix.c
> index 07483e8..173ba4b 100644
> --- a/hw/ide/piix.c
> +++ b/hw/ide/piix.c
> @@ -184,11 +184,13 @@ static PCIDeviceInfo piix_ide_info[] = {
> .qdev.name = "piix3-ide",
> .qdev.size = sizeof(PCIIDEState),
> .qdev.no_user = 1,
> + .no_hotplug = 1,
> .init = pci_piix3_ide_initfn,
> },{
> .qdev.name = "piix4-ide",
> .qdev.size = sizeof(PCIIDEState),
> .qdev.no_user = 1,
> + .no_hotplug = 1,
> .init = pci_piix4_ide_initfn,
> },{
> /* end of list */
> diff --git a/hw/piix4.c b/hw/piix4.c
> index 5489386..1678898 100644
> --- a/hw/piix4.c
> +++ b/hw/piix4.c
> @@ -113,6 +113,7 @@ static PCIDeviceInfo piix4_info[] = {
> .qdev.desc = "ISA bridge",
> .qdev.size = sizeof(PCIDevice),
> .qdev.no_user = 1,
> + .qdev.no_hotplug = 1,
> .init = piix4_initfn,
> },{
> /* end of list */
This one breaks the build for me. The below seems to help - but begs
the question: was this tested?
Thanks,
diff --git a/hw/piix4.c b/hw/piix4.c
index 1678898..00da049 100644
--- a/hw/piix4.c
+++ b/hw/piix4.c
@@ -113,7 +113,7 @@ static PCIDeviceInfo piix4_info[] = {
.qdev.desc = "ISA bridge",
.qdev.size = sizeof(PCIDevice),
.qdev.no_user = 1,
- .qdev.no_hotplug = 1,
+ .no_hotplug = 1,
.init = piix4_initfn,
},{
/* end of list */
next prev parent reply other threads:[~2011-01-05 19:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 13:26 [Qemu-devel] [PATCH 0/3] add hotplug opt-out option for pci devices Gerd Hoffmann
2010-11-30 13:26 ` [Qemu-devel] [PATCH 1/3] pci: allow devices being tagged as not hotpluggable Gerd Hoffmann
2011-01-06 14:53 ` [Qemu-devel] " Michael S. Tsirkin
2010-11-30 13:26 ` [Qemu-devel] [PATCH 2/3] piix: tag " Gerd Hoffmann
2011-01-05 19:44 ` Michael S. Tsirkin [this message]
2011-01-06 8:40 ` [Qemu-devel] " Gerd Hoffmann
2011-01-06 9:29 ` Michael S. Tsirkin
2011-01-06 14:14 ` Gerd Hoffmann
2011-01-06 14:34 ` Michael S. Tsirkin
2011-01-06 18:45 ` Marcelo Tosatti
2011-01-07 11:42 ` Michael S. Tsirkin
2010-11-30 13:26 ` [Qemu-devel] [PATCH 3/3] vga: tag as not hotplugable Gerd Hoffmann
2011-01-05 15:57 ` [Qemu-devel] Re: [PATCH 0/3] add hotplug opt-out option for pci devices Michael S. Tsirkin
2011-01-06 15:17 ` Michael S. Tsirkin
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=20110105194406.GC28688@redhat.com \
--to=mst@redhat.com \
--cc=kraxel@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 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).