From: Isaku Yamahata <yamahata@valinux.co.jp>
To: qemu-devel@nongnu.org
Cc: blauwirbel@gmail.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/4] pci: split out bridge code into pci_bridge and make it library
Date: Thu, 22 Jul 2010 11:33:32 +0900 [thread overview]
Message-ID: <20100722023332.GE8531@valinux.co.jp> (raw)
In-Reply-To: <cover.1278993504.git.yamahata@valinux.co.jp>
Ping?
On Tue, Jul 13, 2010 at 01:01:38PM +0900, Isaku Yamahata wrote:
> Changes v2 -> v1:
v3
> - dropped first patch as it is merdged.
> - rebased to mst's pci branch.
> - eliminated pci_brdige_qdev_register(), pci_brdige_create(),
> pci_brdige_create_simple() by exporting PCIBus and PCIBridge.
>
> Patch description:
> Now pci.c has grown. So split bridge related code into dedicated file
> for further extension to pci bridge. Further clean up and pcie port emulator.
> This make patch conflict less possible in future.
>
> Clean up of pci host bus ans piix pci as discussed with v1
> will be addressed after this patch set is accepted.
>
> changes v1 -> v2:
> - introduce pci_internals.h to accomodate pci internal strcutures to
> share between pci.c and pci_bridge.c
> - don't make PCIBridge::bus pointer as suggested by
> Michael S. Tsirkin <mst@redhat.com>
> - rename PCIBridge::bus -> PCIBridge::sec_bus
> - eliminate pci_reguster_secondary_bus()/pci_unregister_secondary_bus()
> - document pci bridge library functions.
> - introduced pci bridge library.
>
> Isaku Yamahata (4):
> pci/bridge: split out pci bridge code into pci_bridge.c from pci.c
> pci_bridge: rename PCIBridge::bus -> PCIBridge::sec_bus.
> pci_bridge: clean up: remove pci_{register,
> unregister}_secondary_bus()
> pci_bridge: introduce pci bridge library.
>
> Makefile.objs | 2 +-
> hw/apb_pci.c | 56 +++++++++++---
> hw/dec_pci.c | 46 +++++++++--
> hw/pci.c | 177 +-------------------------------------------
> hw/pci.h | 5 +-
> hw/pci_bridge.c | 210 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> hw/pci_bridge.h | 62 +++++++++++++++
> hw/pci_internals.h | 17 +++-
> qemu-common.h | 1 +
> 9 files changed, 369 insertions(+), 207 deletions(-)
> create mode 100644 hw/pci_bridge.c
> create mode 100644 hw/pci_bridge.h
>
>
--
yamahata
next prev parent reply other threads:[~2010-07-22 2:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 4:01 [Qemu-devel] [PATCH v3 0/4] pci: split out bridge code into pci_bridge and make it library Isaku Yamahata
2010-07-13 4:01 ` [Qemu-devel] [PATCH v3 1/4] pci/bridge: split out pci bridge code into pci_bridge.c from pci.c Isaku Yamahata
2010-07-13 4:01 ` [Qemu-devel] [PATCH v3 2/4] pci_bridge: rename PCIBridge::bus -> PCIBridge::sec_bus Isaku Yamahata
2010-07-13 4:01 ` [Qemu-devel] [PATCH v3 3/4] pci_bridge: clean up: remove pci_{register, unregister}_secondary_bus() Isaku Yamahata
2010-07-13 4:01 ` [Qemu-devel] [PATCH v3 4/4] pci_bridge: introduce pci bridge library Isaku Yamahata
2010-07-22 2:33 ` Isaku Yamahata [this message]
2010-07-22 8:28 ` [Qemu-devel] [PATCH v3 0/4] pci: split out bridge code into pci_bridge and make it library Michael S. Tsirkin
2010-07-22 8:51 ` Isaku Yamahata
2010-07-22 9:23 ` 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=20100722023332.GE8531@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=blauwirbel@gmail.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).