From: Isaku Yamahata <yamahata@valinux.co.jp>
To: qemu-devel@nongnu.org
Cc: blauwirbel@gmail.com, yamahata@valinux.co.jp, mst@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] pci: split out bridge code into pci_bridge
Date: Fri, 2 Jul 2010 11:30:10 +0900 [thread overview]
Message-ID: <cover.1278037559.git.yamahata@valinux.co.jp> (raw)
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 (2):
pci/bridge: allocate PCIBus dynamically for PCIBridge.
pci/bridge: split out pci bridge code into pci_bridge.c from pci.c
Makefile.objs | 2 +-
hw/apb_pci.c | 1 +
hw/dec_pci.c | 1 +
hw/pci.c | 177 ++++-------------------------------------------------
hw/pci.h | 9 ++-
hw/pci_bridge.c | 184 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
hw/pci_bridge.h | 41 ++++++++++++
7 files changed, 247 insertions(+), 168 deletions(-)
create mode 100644 hw/pci_bridge.c
create mode 100644 hw/pci_bridge.h
next reply other threads:[~2010-07-02 2:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 2:30 Isaku Yamahata [this message]
2010-07-02 2:30 ` [Qemu-devel] [PATCH 1/2] pci/bridge: allocate PCIBus dynamically for PCIBridge Isaku Yamahata
2010-07-06 12:18 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-07 2:38 ` Isaku Yamahata
2010-07-07 11:47 ` Michael S. Tsirkin
2010-07-08 6:39 ` Isaku Yamahata
2010-07-08 14:04 ` Michael S. Tsirkin
2010-07-08 15:43 ` Isaku Yamahata
2010-07-08 16:49 ` Michael S. Tsirkin
2010-07-09 2:07 ` Isaku Yamahata
2010-07-16 1:46 ` Isaku Yamahata
2010-07-16 7:35 ` Michael S. Tsirkin
2010-07-02 2:30 ` [Qemu-devel] [PATCH 2/2] pci/bridge: split out pci bridge code into pci_bridge.c from pci.c Isaku Yamahata
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=cover.1278037559.git.yamahata@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).