qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: armbru@redhat.com, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, borntraeger@de.ibm.com, afaerber@suse.de,
	anthony@codemonkey.ws, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2 07/10] piix3 piix4: Clean up use of cannot_instantiate_with_device_add_yet
Date: Tue, 29 Oct 2013 10:26:31 -0600	[thread overview]
Message-ID: <526FE1B7.6010707@redhat.com> (raw)
In-Reply-To: <1383062897-30084-8-git-send-email-armbru@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]

On 10/29/2013 10:08 AM, armbru@redhat.com wrote:
> From: Markus Armbruster <armbru@redhat.com>
> 
> A PIIX3/PIIX4 southbridge has multiple functions.  We model each
> function as a separate qdev.  Two of them need some special wiring set
> up in pc_init1() or mips_malta_init() to work: the ISA bridge at 01.0,
> and the SMBus controller at 01.3.
> 
> The IDE controller at 01.1 (piix3-ide, piix3-ide-xen, piix4-ide) has
> always had cannot_instantiate_with_device_add_yet set, but there is no
> obvious reason why device_add could not work for them.  Drop it.

> +++ b/hw/acpi/piix4.c
> @@ -508,9 +508,14 @@ static void piix4_pm_class_init(ObjectClass *klass, void *data)
>      k->revision = 0x03;
>      k->class_id = PCI_CLASS_BRIDGE_OTHER;
>      dc->desc = "PM";
> -    dc->cannot_instantiate_with_device_add_yet = true; /* FIXME explain why */
> +    dc->cannot_instantiate_with_device_add_yet = true;
>      dc->vmsd = &vmstate_acpi;
>      dc->props = piix4_pm_properties;
> +    /*
> +     * Reason: part of PIIX4 southbridge, needs to be wired up,
> +     * e.g. by mips_malta_init()
> +     */
> +    dc->cannot_instantiate_with_device_add_yet = true;

Is it intentional that you initialize the field twice to the same value?

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  reply	other threads:[~2013-10-29 16:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 16:08 [Qemu-devel] [PATCH v2 00/10] Clean up and fix no_user armbru
2013-10-29 16:08 ` [Qemu-devel] [PATCH v2 01/10] qdev: Replace no_user by cannot_instantiate_with_device_add_yet armbru
2013-10-30  9:45   ` Marcel Apfelbaum
2013-10-30 12:21     ` Markus Armbruster
2013-10-29 16:08 ` [Qemu-devel] [PATCH v2 02/10] sysbus: Set cannot_instantiate_with_device_add_yet armbru
2013-10-30 10:13   ` Marcel Apfelbaum
2013-10-29 16:08 ` [Qemu-devel] [PATCH v2 03/10] cpu: Document why cannot_instantiate_with_device_add_yet armbru
2013-10-29 16:08 ` [Qemu-devel] [PATCH v2 04/10] apic: " armbru
2013-10-29 16:08 ` [Qemu-devel] [PATCH v2 05/10] pci-host: Consistently set cannot_instantiate_with_device_add_yet armbru
2013-10-30  9:45   ` Marcel Apfelbaum
2013-10-30 12:30     ` Markus Armbruster
2013-10-30 13:12       ` Andreas Färber
2013-10-30 13:54         ` Markus Armbruster
2013-10-30 14:30           ` Marcel Apfelbaum
2013-10-29 16:08 ` [Qemu-devel] [PATCH v2 06/10] ich9: Document why cannot_instantiate_with_device_add_yet armbru
2013-10-29 16:08 ` [Qemu-devel] [PATCH v2 07/10] piix3 piix4: Clean up use of cannot_instantiate_with_device_add_yet armbru
2013-10-29 16:26   ` Eric Blake [this message]
2013-10-29 17:37     ` Markus Armbruster
2013-10-29 16:08 ` [Qemu-devel] [PATCH v2 08/10] vt82c686: " armbru
2013-10-29 16:08 ` [Qemu-devel] [PATCH v2 09/10] isa: " armbru
2013-10-29 16:08 ` [Qemu-devel] [PATCH v2 10/10] qdev: Do not let the user try to device_add when it cannot work armbru
2013-10-30  9:45   ` Marcel Apfelbaum
2013-10-30 12:15     ` Markus Armbruster
2013-10-30 14:20       ` Marcel Apfelbaum
2013-10-30 14:49         ` Markus Armbruster

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=526FE1B7.6010707@redhat.com \
    --to=eblake@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).