From: "Michael S. Tsirkin" <mst@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v2 0/5] pci: split out bridge code into pci_bridge and make it library
Date: Mon, 12 Jul 2010 15:11:07 +0300 [thread overview]
Message-ID: <20100712121107.GB31649@redhat.com> (raw)
In-Reply-To: <cover.1278930415.git.yamahata@valinux.co.jp>
On Mon, Jul 12, 2010 at 07:36:39PM +0900, Isaku Yamahata wrote:
> 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.
I've applied patches 1-4 to make it easier to build upon.
Pushed in pci branch in my tree.
Sent comments on patch 5.
> Clean up of pci host bus ans piix pci as discussed with v1
> will be addressed after this patch set is accepted.
>
> 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.
>
> Isaku Yamahata (5):
> pci: move out pci internal structures, PCIBus, PCIBridge, and
> pci_bus_info.
> 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 | 43 ++++++---
> hw/dec_pci.c | 35 ++++++--
> hw/pci.c | 207 +------------------------------------------
> hw/pci.h | 5 +-
> hw/pci_bridge.c | 249 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> hw/pci_bridge.h | 62 +++++++++++++
> hw/pci_internals.h | 42 +++++++++
> qemu-common.h | 1 +
> 9 files changed, 416 insertions(+), 230 deletions(-)
> create mode 100644 hw/pci_bridge.c
> create mode 100644 hw/pci_bridge.h
> create mode 100644 hw/pci_internals.h
prev parent reply other threads:[~2010-07-12 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 10:36 [Qemu-devel] [PATCH v2 0/5] pci: split out bridge code into pci_bridge and make it library Isaku Yamahata
2010-07-12 10:36 ` [Qemu-devel] [PATCH v2 1/5] pci: move out pci internal structures, PCIBus, PCIBridge, and pci_bus_info Isaku Yamahata
2010-07-12 10:36 ` [Qemu-devel] [PATCH v2 2/5] pci/bridge: split out pci bridge code into pci_bridge.c from pci.c Isaku Yamahata
2010-07-12 12:16 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-12 13:22 ` Isaku Yamahata
2010-07-12 10:36 ` [Qemu-devel] [PATCH v2 3/5] pci_bridge: rename PCIBridge::bus -> PCIBridge::sec_bus Isaku Yamahata
2010-07-12 10:36 ` [Qemu-devel] [PATCH v2 4/5] pci_bridge: clean up: remove pci_{register, unregister}_secondary_bus() Isaku Yamahata
2010-07-12 10:36 ` [Qemu-devel] [PATCH v2 5/5] pci_bridge: introduce pci bridge library Isaku Yamahata
2010-07-12 12:10 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-12 13:28 ` Isaku Yamahata
2010-07-12 14:47 ` Michael S. Tsirkin
2010-07-12 12:11 ` Michael S. Tsirkin [this message]
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=20100712121107.GB31649@redhat.com \
--to=mst@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).