From: Wanpeng Li <liwp@linux.vnet.ibm.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/6] refactor PC machine, i440fx and piix3 to take advantage of QOM
Date: Mon, 26 Mar 2012 20:57:57 +0800 [thread overview]
Message-ID: <20120326125757.GA17898@liwp@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F706557.4040305@suse.de>
On Mon, Mar 26, 2012 at 02:47:19PM +0200, Andreas Färber wrote:
>Am 26.03.2012 04:06, schrieb Wanpeng Li:
>> From: Anthony Liguori <aliguori@us.ibm.com>
>
>Resending an old cover letter is not a good idea. This looks like a v2,
>so please mark it as such in the subjects; it's missing a Change Log
>against Anthony's version. I take it, some patches were dropped?
>
No, I just help him rebase his patches.
>> This series aggressively refactors the PC machine initialization to be more
>> modelled and less ad-hoc. The highlights of this series are:
>>
>> 1) Things like -m and -bios-name are now device model properties
>>
>> 2) The i440fx and piix3 are now modelled in a thorough fashion
>>
>> 3) Most of the chipset features of the piix3 are modelled through composition
>>
>> 4) i440fx_init is trivialized to creating devices and setting properties
>>
>> 5) convert MemoryRegion to QOM
>>
>> 6) convert PCI host bridge to QOM
>>
>> The point (4) is the most important one. As we refactor in this fashion,
>> we should quickly get to the point where machine->init disappears completely in
>> favor of just creating a handful of devices.
>
>I agree that machine->init needs to be refactored, however I don't think
>it'll disappear, just be moved into initfn/realize functions.
>
>Andreas
>
>>
>> The two stage initialization of QOM is important here. instance_init() is when
>> composed devices are created which means that after you've created a device, all
>> of its children are visible in the device model. This lets you set properties
>> of the parent and its children.
>>
>> realize() (which is still called DeviceState::init today) will be called right
>> before the guest starts up for the first time.
>>
>> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>> Signed-off-by: Wanpeng Li <liwp@linux.vnet.ibm.com>
>>
>> ---
>> Makefile.target | 3 +-
>> hw/hpet.c | 39 +---
>> hw/hpet_emul.h | 41 +++
>> hw/i440fx.c | 431 ++++++++++++++++++++++++++
>> hw/i440fx.h | 78 +++++
>> hw/i8254_internal.h | 2 +-
>> hw/mc146818rtc.c | 26 --
>> hw/mc146818rtc.h | 29 ++
>> hw/pc.c | 838 +++++++++++++++++++++++++++++++++++++++++++++------
>> hw/pc.h | 46 +---
>> hw/pc_piix.c | 762 ----------------------------------------------
>> hw/pci_host.c | 26 ++
>> hw/pci_host.h | 5 +
>> hw/piix3.c | 274 +++++++++++++++++
>> hw/piix3.h | 79 +++++
>> hw/piix_pci.c | 600 ------------------------------------
>> memory.c | 94 +++++--
>> memory.h | 8 +
>> 18 files changed, 1795 insertions(+), 1586 deletions(-)
>> create mode 100644 hw/i440fx.c
>> create mode 100644 hw/i440fx.h
>> delete mode 100644 hw/pc_piix.c
>> create mode 100644 hw/piix3.c
>> create mode 100644 hw/piix3.h
>> delete mode 100644 hw/piix_pci.c
>> --
>
>--
>SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
>
--
LTC China, IBM, Shanghai
next prev parent reply other threads:[~2012-03-26 12:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 2:06 [Qemu-devel] [PATCH 0/6] refactor PC machine, i440fx and piix3 to take advantage of QOM Wanpeng Li
2012-03-26 2:06 ` [Qemu-devel] [PATCH 1/6] eliminate piix_pci.c and module i440fx and piix3 Wanpeng Li
2012-03-26 2:06 ` [Qemu-devel] [PATCH 2/6] convert MemoryRegion to QOM Wanpeng Li
2012-03-26 2:06 ` [Qemu-devel] [PATCH 3/6] convert pci-host " Wanpeng Li
2012-03-26 7:32 ` Stefan Hajnoczi
2012-03-26 9:22 ` Wanpeng Li
2012-03-26 14:25 ` Andreas Färber
2012-03-26 2:06 ` [Qemu-devel] [PATCH 4/6] prepare to create HPET, RTC and i8254 through composition Wanpeng Li
2012-03-26 2:06 ` [Qemu-devel] [PATCH 5/6] merge pc_piix.c to pc.c Wanpeng Li
2012-03-26 12:42 ` Avi Kivity
2012-03-26 12:47 ` Jan Kiszka
2012-03-26 17:37 ` Anthony Liguori
2012-03-26 2:06 ` [Qemu-devel] [PATCH 6/6] make some functions static Wanpeng Li
2012-03-26 12:20 ` [Qemu-devel] [PATCH 0/6] refactor PC machine, i440fx and piix3 to take advantage of QOM Jan Kiszka
2012-03-26 15:54 ` Isaku Yamahata
2012-03-26 17:29 ` Anthony Liguori
2012-03-27 10:31 ` Avi Kivity
2012-03-27 13:52 ` Anthony Liguori
2012-03-27 14:18 ` Avi Kivity
2012-03-26 17:17 ` Blue Swirl
2012-03-26 17:33 ` Anthony Liguori
2012-03-26 19:30 ` Jan Kiszka
2012-03-26 19:35 ` Anthony Liguori
2012-03-26 19:37 ` Jan Kiszka
2012-03-26 19:39 ` Anthony Liguori
2012-03-26 19:44 ` Jan Kiszka
2012-03-26 19:49 ` Anthony Liguori
2012-03-26 20:10 ` Jan Kiszka
2012-03-26 20:13 ` Anthony Liguori
2012-03-26 20:30 ` Jan Kiszka
2012-03-26 21:00 ` Anthony Liguori
2012-03-26 19:52 ` Anthony Liguori
2012-03-26 12:47 ` Andreas Färber
2012-03-26 12:57 ` Wanpeng Li [this message]
2012-03-26 17:09 ` Blue Swirl
2012-03-26 17:35 ` Anthony Liguori
2012-03-26 17:43 ` Blue Swirl
2012-03-26 17:45 ` Anthony Liguori
2012-03-26 18:01 ` Blue Swirl
2012-03-26 18:07 ` Anthony Liguori
2012-03-26 18:25 ` Blue Swirl
2012-03-26 17:25 ` Anthony Liguori
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=20120326125757.GA17898@liwp@linux.vnet.ibm.com \
--to=liwp@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--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).