From: Marcel Apfelbaum <marcel.a@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, famz@redhat.com, stefanha@redhat.com,
mst@redhat.com, alex@alex.org.uk, armbru@redhat.com,
stefano.stabellini@eu.citrix.com, agraf@suse.de,
lcapitulino@redhat.com, aliguori@amazon.com, pbonzini@redhat.com,
afaerber@suse.de, rth@twiddle.net
Subject: [Qemu-devel] [PATCH V2 0/5] remove QEMUMachine indirection from MachineClass
Date: Mon, 31 Mar 2014 12:26:28 +0300 [thread overview]
Message-ID: <1396257993-4036-1-git-send-email-marcel.a@redhat.com> (raw)
V1 -> V2:
- Addressed Paolo's comments:
- replaced commas by semicolons on patch 4/5.
- Rebased to master.
This is a continuation of 'QEMU Machine as QOM object' effort.
The scope of this series is to allow machine QOM-ification
of all machines gradually, by removing the need for QEMUMachine registration through vl.c .
Now we will have 2 paths:
1. Non QOM-ified machines will be converted to QOM on the fly
in vl.c by qemu machine registration.
2. QOM-ified machines will behave as regular QOM classes setting
MachineClass fields in class_init.
- Patch 4/5 demonstrates this.
Next steps:
- Replace QemuOpts queries by MachineState fields.
- Follow Paolo's suggestions to get rid of QEMUMachineInitArgs.
Comments are appreciated,
Thanks,
Marcel
Marcel Apfelbaum (5):
hw/boards.h: add QEMUMachine's fields to MachineClass
machine: remove QEMUMachine indirection from MachineClass
machine: replace QEMUMachine by MachineClass in accelerator
configuration
hw/ppc: remove QEMUMachine indirection
vl.c: Remove QEMUMachine usage
device-hotplug.c | 2 +-
hw/ppc/spapr.c | 26 +++++------
include/hw/boards.h | 30 +++++++++++--
include/hw/xen/xen.h | 2 +-
include/qemu/typedefs.h | 1 +
include/sysemu/kvm.h | 2 +-
include/sysemu/qtest.h | 2 +-
kvm-all.c | 6 +--
kvm-stub.c | 2 +-
qmp.c | 4 +-
qtest.c | 2 +-
vl.c | 114 +++++++++++++++++++++++++++---------------------
xen-all.c | 2 +-
xen-stub.c | 2 +-
14 files changed, 116 insertions(+), 81 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-03-31 9:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 9:26 Marcel Apfelbaum [this message]
2014-03-31 9:26 ` [Qemu-devel] [PATCH V2 1/5] hw/boards.h: add QEMUMachine's fields to MachineClass Marcel Apfelbaum
2014-03-31 9:26 ` [Qemu-devel] [PATCH V2 2/5] machine: remove QEMUMachine indirection from MachineClass Marcel Apfelbaum
2014-04-03 16:59 ` Andreas Färber
2014-04-03 17:11 ` Marcel Apfelbaum
2014-04-03 17:36 ` Andreas Färber
2014-04-03 17:40 ` Marcel Apfelbaum
2014-03-31 9:26 ` [Qemu-devel] [PATCH V2 3/5] machine: replace QEMUMachine by MachineClass in accelerator configuration Marcel Apfelbaum
2014-03-31 9:26 ` [Qemu-devel] [PATCH V2 4/5] hw/ppc: remove QEMUMachine indirection Marcel Apfelbaum
2014-04-03 17:25 ` Andreas Färber
2014-04-03 17:46 ` Marcel Apfelbaum
2014-04-03 17:57 ` Andreas Färber
2014-04-03 18:08 ` Marcel Apfelbaum
2014-03-31 9:26 ` [Qemu-devel] [PATCH V2 5/5] vl.c: Remove QEMUMachine usage Marcel Apfelbaum
2014-04-03 17:09 ` Andreas Färber
2014-04-03 17:12 ` Marcel Apfelbaum
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=1396257993-4036-1-git-send-email-marcel.a@redhat.com \
--to=marcel.a@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=alex@alex.org.uk \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.com \
--cc=stefano.stabellini@eu.citrix.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).