From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Alexander Graf" <agraf@suse.de>,
"Andreas Färber" <andreas.faerber@web.de>,
"Hervé Poussineau" <hpoussin@reactos.org>,
anthony@codemonkey.ws, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH prep for-1.4? v2 0/2] prep_pci: Prepare for QOM realize
Date: Wed, 16 Jan 2013 16:11:45 +0100 [thread overview]
Message-ID: <1358349107-19592-1-git-send-email-afaerber@suse.de> (raw)
From: Andreas Färber <andreas.faerber@web.de>
Hello Anthony and Paolo,
Here's a respin of the patch that prompted the big PCI host bridge refactoring.
It embeds PCIBus and PCIDevice into the host bridge state QOM-style.
Question: Is the use of object_unref() correct and future-proof now?
I'm also adding a second patch even more as an example of what is possible with
QOM types and now QOM realize: New SysBusDevices (e.g., IDE refactoring) can get
a realizefn straight away!
Regards,
Andreas
v1 -> v2:
* Rebased onto PCI header reorganization (pci_internal.h -> pci/pci_bus.h).
* Replaced privatized object_finalize() with object_unref().
* Added patch converting initfn to realizefn.
Cc: Anthony Liguori <anthony@codemonkey.ws>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>
Cc: Alexander Graf <agraf@suse.de>
Cc: Hervé Poussineau <hpoussin@reactos.org>
Andreas Färber (2):
prep_pci: Create PCIBus and PCIDevice in-place
prep_pci: Convert to QOM realizefn
hw/prep_pci.c | 65 +++++++++++++++++++++++++++++++++++++++++++--------------
1 Datei geändert, 49 Zeilen hinzugefügt(+), 16 Zeilen entfernt(-)
--
1.7.10.4
next reply other threads:[~2013-01-16 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 15:11 Andreas Färber [this message]
2013-01-16 15:11 ` [Qemu-devel] [PATCH prep for-1.4? v2 1/2] prep_pci: Create PCIBus and PCIDevice in-place Andreas Färber
2013-01-16 15:11 ` [Qemu-devel] [PATCH prep for-1.4? v2 2/2] prep_pci: Convert to QOM realizefn Andreas Färber
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=1358349107-19592-1-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=andreas.faerber@web.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=hpoussin@reactos.org \
--cc=pbonzini@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).