From: David Gibson <david@gibson.dropbear.id.au>
To: mst@redhat.com, ehabkost@redhat.com, marcel@redhat.com
Cc: qemu-devel@nongnu.org, alex.williamson@redhat.com,
David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [RFC 0/5] Assorted PCI/PCIe cleanups cleanups
Date: Tue, 3 Oct 2017 20:14:18 +1100 [thread overview]
Message-ID: <20171003091423.28704-1-david@gibson.dropbear.id.au> (raw)
I've been reworking my patches to consolidate the handling of PCI/PCIe
"hybrid" devices based on feedback from my earlier series. I'm still
wrestling with some problems here, but along the way I've made some
cleanups which I think stand on their own. So, here they are.
I built these on top of Eduardo's series to advertise PCI and PCIe
capability of devices via interface names. I don't think I
fundamentally rely on anything in there, but if there are conflicts
against master, that'd be why.
David Gibson (5):
pci: Rename root bus initialization functions for clarity
pci: Move bridge data structures from pci_bus.h to pci_bridge.h
pci: Fold pci_bus.h into pci.h
pci: Simplify pci_bus_is_root()
pcie: Don't allow extended config space access via conventional PCI
bridges
hw/acpi/pcihp.c | 1 -
hw/alpha/typhoon.c | 8 ++--
hw/i386/acpi-build.c | 1 -
hw/i386/amd_iommu.h | 1 -
hw/i386/intel_iommu.c | 1 -
hw/i386/pc.c | 1 -
hw/isa/lpc_ich9.c | 1 -
hw/mips/gt64xxx_pci.c | 12 ++---
hw/pci-bridge/dec.c | 1 -
hw/pci-bridge/pci_bridge_dev.c | 1 -
hw/pci-bridge/pci_expander_bridge.c | 11 +----
hw/pci-bridge/pcie_pci_bridge.c | 1 -
hw/pci-host/apb.c | 11 ++---
hw/pci-host/bonito.c | 8 ++--
hw/pci-host/gpex.c | 6 +--
hw/pci-host/grackle.c | 14 +++---
hw/pci-host/piix.c | 4 +-
hw/pci-host/ppce500.c | 6 +--
hw/pci-host/prep.c | 5 +-
hw/pci-host/q35.c | 7 +--
hw/pci-host/uninorth.c | 24 +++++-----
hw/pci-host/versatile.c | 7 ++-
hw/pci-host/xilinx-pcie.c | 6 +--
hw/pci/pci.c | 71 ++++++++++++++--------------
hw/pci/pci_bridge.c | 1 -
hw/pci/pci_host.c | 1 -
hw/pci/pcie.c | 1 -
hw/pci/pcie_aer.c | 1 -
hw/pci/shpc.c | 1 -
hw/ppc/ppc4xx_pci.c | 6 +--
hw/ppc/spapr_pci.c | 9 ++--
hw/s390x/s390-pci-bus.c | 9 ++--
hw/sh4/sh_pci.c | 12 ++---
include/hw/i386/ich9.h | 1 -
include/hw/pci-host/xilinx-pcie.h | 2 +-
include/hw/pci/pci.h | 91 ++++++++++++++++++++++++++++-------
include/hw/pci/pci_bridge.h | 47 +++++++++++++++++++
include/hw/pci/pci_bus.h | 94 -------------------------------------
include/hw/pci/pcie_port.h | 1 -
39 files changed, 237 insertions(+), 249 deletions(-)
delete mode 100644 include/hw/pci/pci_bus.h
--
2.13.6
next reply other threads:[~2017-10-03 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 9:14 David Gibson [this message]
2017-10-03 9:14 ` [Qemu-devel] [RFC 1/5] pci: Rename root bus initialization functions for clarity David Gibson
2017-10-03 9:14 ` [Qemu-devel] [RFC 2/5] pci: Move bridge data structures from pci_bus.h to pci_bridge.h David Gibson
2017-10-03 9:14 ` [Qemu-devel] [RFC 3/5] pci: Fold pci_bus.h into pci.h David Gibson
2017-10-03 9:14 ` [Qemu-devel] [RFC 4/5] pci: Simplify pci_bus_is_root() David Gibson
2017-10-03 14:42 ` Eduardo Habkost
2017-10-04 6:03 ` David Gibson
2017-10-03 9:14 ` [Qemu-devel] [RFC 5/5] pcie: Don't allow extended config space access via conventional PCI bridges David Gibson
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=20171003091423.28704-1-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=alex.williamson@redhat.com \
--cc=ehabkost@redhat.com \
--cc=marcel@redhat.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).