From: Tiejun Chen <tiejun.chen@intel.com>
To: mst@redhat.com
Cc: pbonzini@redhat.com, xen-devel@lists.xensource.com,
qemu-devel@nongnu.org, stefano.stabellini@eu.citrix.com
Subject: [Qemu-devel] [v2][PATCH 2/5] hw:pci-host:piix: split i440fx_init
Date: Thu, 31 Jul 2014 14:31:36 +0800 [thread overview]
Message-ID: <1406788299-8394-3-git-send-email-tiejun.chen@intel.com> (raw)
In-Reply-To: <1406788299-8394-1-git-send-email-tiejun.chen@intel.com>
We'd like to split i440fx_init and then we can share something
with other stuff.
Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
---
hw/pci-host/piix.c | 91 ++++++++++++++++++++++++++++++++++++++++++++----------
1 file changed, 75 insertions(+), 16 deletions(-)
v2:
* New patch to separate i440fx_init
diff --git a/hw/pci-host/piix.c b/hw/pci-host/piix.c
index e0e0946..a9a5570 100644
--- a/hw/pci-host/piix.c
+++ b/hw/pci-host/piix.c
@@ -305,25 +305,14 @@ static int i440fx_initfn(PCIDevice *dev)
return 0;
}
-PCIBus *i440fx_init(PCII440FXState **pi440fx_state,
- int *piix3_devfn,
- ISABus **isa_bus, qemu_irq *pic,
- MemoryRegion *address_space_mem,
- MemoryRegion *address_space_io,
- ram_addr_t ram_size,
- ram_addr_t below_4g_mem_size,
- ram_addr_t above_4g_mem_size,
- MemoryRegion *pci_address_space,
- MemoryRegion *ram_memory)
+static void i440fx_pci_host_create(DeviceState **dev_bridge,
+ PCIBus **bus_bridge,
+ MemoryRegion *address_space_io,
+ MemoryRegion *pci_address_space)
{
DeviceState *dev;
PCIBus *b;
- PCIDevice *d;
PCIHostState *s;
- PIIX3State *piix3;
- PCII440FXState *f;
- unsigned i;
- I440FXState *i440fx;
dev = qdev_create(NULL, TYPE_I440FX_PCI_HOST_BRIDGE);
s = PCI_HOST_BRIDGE(dev);
@@ -333,8 +322,48 @@ PCIBus *i440fx_init(PCII440FXState **pi440fx_state,
object_property_add_child(qdev_get_machine(), "i440fx", OBJECT(dev), NULL);
qdev_init_nofail(dev);
- d = pci_create_simple(b, 0, TYPE_I440FX_PCI_DEVICE);
+ *bus_bridge = b;
+ *dev_bridge = dev;
+}
+
+static PCIDevice *i440fx_pci0_create(PCIBus **bus_bridge,
+ const char *type,
+ PCII440FXState **pi440fx_state)
+{
+ PCIBus *b;
+ PCIDevice *d;
+
+ b = *bus_bridge;
+
+ d = pci_create_simple(b, 0, type);
*pi440fx_state = I440FX_PCI_DEVICE(d);
+ return d;
+}
+
+static PCIBus *i440fx_pci_setup(DeviceState **dev_bridge,
+ PCIBus **bus_bridge,
+ PCIDevice *d,
+ PCII440FXState **pi440fx_state,
+ int *piix3_devfn,
+ ISABus **isa_bus, qemu_irq *pic,
+ MemoryRegion *address_space_mem,
+ MemoryRegion *address_space_io,
+ ram_addr_t ram_size,
+ ram_addr_t below_4g_mem_size,
+ ram_addr_t above_4g_mem_size,
+ MemoryRegion *pci_address_space,
+ MemoryRegion *ram_memory)
+{
+ DeviceState *dev;
+ PCIBus *b;
+ PCII440FXState *f;
+ I440FXState *i440fx;
+ unsigned i;
+ PIIX3State *piix3;
+
+ b = *bus_bridge;
+ dev = *dev_bridge;
+
f = *pi440fx_state;
f->system_memory = address_space_mem;
f->pci_address_space = pci_address_space;
@@ -392,6 +421,36 @@ PCIBus *i440fx_init(PCII440FXState **pi440fx_state,
return b;
}
+PCIBus *i440fx_init(PCII440FXState **pi440fx_state,
+ int *piix3_devfn,
+ ISABus **isa_bus,
+ qemu_irq *pic,
+ MemoryRegion *address_space_mem,
+ MemoryRegion *address_space_io,
+ ram_addr_t ram_size,
+ ram_addr_t below_4g_mem_size,
+ ram_addr_t above_4g_mem_size,
+ MemoryRegion *pci_address_space,
+ MemoryRegion *ram_memory)
+{
+ PCIDevice *d;
+ DeviceState *dev_bridge;
+ PCIBus *bus_bridge;
+
+ i440fx_pci_host_create(&dev_bridge, &bus_bridge, address_space_io,
+ pci_address_space);
+
+ d = i440fx_pci0_create(&bus_bridge, TYPE_I440FX_PCI_DEVICE, pi440fx_state);
+
+ bus_bridge = i440fx_pci_setup(&dev_bridge, &bus_bridge, d, pi440fx_state,
+ piix3_devfn, isa_bus, pic, address_space_mem,
+ address_space_io, ram_size, below_4g_mem_size,
+ above_4g_mem_size, pci_address_space,
+ ram_memory);
+
+ return bus_bridge;
+}
+
PCIBus *find_i440fx(void)
{
PCIHostState *s = OBJECT_CHECK(PCIHostState,
--
1.9.1
next prev parent reply other threads:[~2014-07-31 6:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 6:31 [Qemu-devel] [v2][PATCH 0/5] xen: introduce new machine for IGD passthrough Tiejun Chen
2014-07-31 6:31 ` [Qemu-devel] [v2][PATCH 1/5] hw:i386:pc_piix: split pc_init1() Tiejun Chen
2014-07-31 6:31 ` Tiejun Chen [this message]
2014-07-31 9:10 ` [Qemu-devel] [v2][PATCH 2/5] hw:pci-host:piix: split i440fx_init Michael S. Tsirkin
2014-07-31 9:26 ` Chen, Tiejun
2014-07-31 9:53 ` Michael S. Tsirkin
2014-07-31 10:12 ` Chen, Tiejun
2014-07-31 12:10 ` Chen, Tiejun
2014-07-31 15:47 ` Michael S. Tsirkin
2014-08-01 2:40 ` Chen, Tiejun
2014-07-31 15:44 ` Michael S. Tsirkin
2014-08-01 2:35 ` Chen, Tiejun
2014-08-04 7:11 ` Chen, Tiejun
2014-07-31 6:31 ` [Qemu-devel] [v2][PATCH 3/5] xen:hw:pci-host:piix: create host bridge to passthrough Tiejun Chen
2014-07-31 6:31 ` [Qemu-devel] [v2][PATCH 4/5] xen:hw:pci-host:piix: introduce xen_igd_passthrough_i440fx_init Tiejun Chen
2014-07-31 6:31 ` [Qemu-devel] [v2][PATCH 5/5] xen:hw:i386:pc_piix: introduce new machine for IGD passthrough Tiejun Chen
2014-07-31 8:58 ` [Qemu-devel] [v2][PATCH 0/5] xen: " Michael S. Tsirkin
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=1406788299-8394-3-git-send-email-tiejun.chen@intel.com \
--to=tiejun.chen@intel.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).