From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "Marcel Apfelbaum" <marcel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: [Qemu-devel] [PATCH 0/6] machine: Deprecate machine_init()
Date: Sat, 19 Sep 2015 17:36:37 +0200 [thread overview]
Message-ID: <1442677004-4482-1-git-send-email-afaerber@suse.de> (raw)
Hello,
Based on my pending qom-next pull, this series continues Eduardo's machine cleanups.
Having eliminated QEMUMachine and qemu_machine_register(), this series eliminates
machine_init() and MODULE_INIT_MACHINE.
As a side effect a few non-machine callers had to be updated, mostly for QemuOpts.
It goes on to update Exynos4 machines for QOM, demonstrating that DEFINE_MACHINE()
can be inferior to inlining the QOM boilerplate code in case of multiple machines.
Independently, I noticed a nit in the PC machine macro I'm touching that could
probably even be cherry-picked.
Regards,
Andreas
Cc: Eduardo Habkost <ehabkost@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Andreas Färber (6):
Use type_init() for all machine QOM types
hw/s390x/css: Use type_init() instead of machine_init()
Introduce config_init() for QemuOpts
Drop machine_init() and MODULE_INIT_MACHINE
exynos4: Further QOM'ify machines
pc: Use type_register_static() for machine types
fsdev/qemu-fsdev-opts.c | 2 +-
hw/acpi/core.c | 2 +-
hw/arm/exynos4_boards.c | 73 ++++++++++++++++++++++++++-----------------------
hw/arm/gumstix.c | 2 +-
hw/arm/highbank.c | 2 +-
hw/arm/nseries.c | 2 +-
hw/arm/omap_sx1.c | 2 +-
hw/arm/realview.c | 2 +-
hw/arm/spitz.c | 15 ++++------
hw/arm/stellaris.c | 11 ++------
hw/arm/versatilepb.c | 11 ++------
hw/arm/vexpress.c | 2 +-
hw/arm/virt.c | 2 +-
hw/lm32/lm32_boards.c | 2 +-
hw/mips/mips_jazz.c | 2 +-
hw/ppc/ppc405_boards.c | 2 +-
hw/s390x/css.c | 2 +-
hw/smbios/smbios.c | 2 +-
hw/sparc/sun4m.c | 14 ++++------
hw/sparc64/sun4u.c | 12 +++-----
hw/xtensa/xtfpga.c | 2 +-
include/hw/boards.h | 2 +-
include/hw/i386/pc.h | 4 +--
include/qemu/module.h | 4 +--
ui/spice-core.c | 2 +-
ui/vnc.c | 2 +-
vl.c | 3 +-
27 files changed, 83 insertions(+), 100 deletions(-)
--
2.1.4
next reply other threads:[~2015-09-19 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 15:36 Andreas Färber [this message]
2015-09-19 15:36 ` [Qemu-devel] [PATCH 1/6] Use type_init() for all machine QOM types Andreas Färber
2015-09-19 15:36 ` [Qemu-devel] [PATCH 2/6] hw/s390x/css: Use type_init() instead of machine_init() Andreas Färber
2015-09-21 8:04 ` Christian Borntraeger
2015-09-19 15:36 ` [Qemu-devel] [PATCH 3/6] Introduce config_init() for QemuOpts Andreas Färber
2015-09-19 15:36 ` [Qemu-devel] [PATCH 4/6] Drop machine_init() and MODULE_INIT_MACHINE Andreas Färber
2015-09-19 15:36 ` [Qemu-devel] [PATCH 5/6] exynos4: Further QOM'ify machines Andreas Färber
2015-09-19 15:36 ` [Qemu-devel] [PATCH 6/6] pc: Use type_register_static() for machine types Andreas Färber
2015-09-21 15:53 ` [Qemu-devel] [PATCH 0/6] machine: Deprecate machine_init() Eduardo Habkost
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=1442677004-4482-1-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@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).