From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Ram Pai <pair@us.ibm.com>, "Michael S. Tsirkin" <mst@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, Liu Ping Fan <kernelfans@gmail.com>,
Blue Swirl <blauwirbel@gmail.com>,
Stefan Weil <weil@mail.berlios.de>, Avi Kivity <avi@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Wanpeng Li <liwanp@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 00/10] piix3: create all child devices as proper QOM children
Date: Thu, 8 Nov 2012 13:36:29 +0800 [thread overview]
Message-ID: <1352352999-2561-1-git-send-email-liwanp@linux.vnet.ibm.com> (raw)
All of the devices described in the PIIX3 as being implemented within the
PIIX3 are created as child devices of the PIIX3 object in QEMU.
PIIX3 has-a RTC, has-a I8042, has-a PCSPK, etc.
All child device creation for the PIIX3 is done by calling object_init()
with qdev_init() being called for each child device in the PIIX3 ::init
function.
Anthony Liguori (3):
convert RTC as piix3 proper QOM child
convert HPET as piix3 proper QOM child
convert PIT as piix3 proper QOM child
Wanpeng Li (7):
convert PCSPK as piix3 proper QOM child
convert PORT92 as piix3 proper QOM child
convert I8042 as piixe proper QOM child
convert VMPORT piix3 proper QOM child
convert VMMOUSE as piix3 proper QOM child
convert IDE as piix3 proper QOM child
convert IOAPIC as piix3 proper QOM child
hw/hpet.c | 35 ---------
hw/hpet_emul.h | 40 ++++++++++
hw/i440fx.c | 6 ++
hw/i8254.c | 2 +-
hw/i8254_internal.h | 3 +-
hw/ide.h | 6 +-
hw/ide/internal.h | 9 ++
hw/ide/isa.c | 14 +---
hw/ide/piix.c | 24 +------
hw/ioapic.c | 2 +-
hw/ioapic.h | 2 -
hw/ioapic_internal.h | 2 +
hw/kvm/i8254.c | 8 +--
hw/kvm/ioapic.c | 9 +--
hw/mc146818rtc.c | 29 +-------
hw/mc146818rtc.h | 30 +++++++
hw/pc.c | 144 ++++-------------------------------
hw/pc.h | 14 ++-
hw/pckbd.c | 24 +------
hw/pcspk.c | 19 +-----
hw/pcspk.h | 19 +++++
hw/piix3.c | 205 ++++++++++++++++++++++++++++++++++++++++++++++++++
hw/piix3.h | 104 +++++++++++++++++++++++++
hw/ps2.h | 3 +
hw/vmmouse.c | 14 ----
hw/vmport.c | 10 +--
sysemu.h | 2 -
27 files changed, 459 insertions(+), 320 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-11-08 5:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 5:36 Wanpeng Li [this message]
2012-11-08 5:36 ` [Qemu-devel] [PATCH 01/10] convert RTC as piix3 proper QOM child Wanpeng Li
2012-11-08 5:36 ` [Qemu-devel] [PATCH 02/10] convert HPET " Wanpeng Li
2012-11-08 5:36 ` [Qemu-devel] [PATCH 03/10] convert PIT " Wanpeng Li
2012-11-08 5:36 ` [Qemu-devel] [PATCH 04/10] convert PCSPK " Wanpeng Li
2012-11-08 5:36 ` [Qemu-devel] [PATCH 05/10] convert PORT92 " Wanpeng Li
2012-11-08 5:36 ` [Qemu-devel] [PATCH 06/10] convert i8042 " Wanpeng Li
2012-11-08 5:36 ` [Qemu-devel] [PATCH 07/10] convert VMPORT " Wanpeng Li
2012-11-08 5:36 ` [Qemu-devel] [PATCH 08/10] convert VMMOUSE " Wanpeng Li
2012-11-08 5:36 ` [Qemu-devel] [PATCH 09/10] convert IDE " Wanpeng Li
2012-11-08 5:36 ` [Qemu-devel] [PATCH 10/10] convert IOAPIC " Wanpeng Li
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=1352352999-2561-1-git-send-email-liwanp@linux.vnet.ibm.com \
--to=liwanp@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kernelfans@gmail.com \
--cc=mst@redhat.com \
--cc=pair@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).