All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: mst@redhat.com, qemu-devel@nongnu.org
Cc: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	mdroth@linux.vnet.ibm.com,
	David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCH 0/2] Some small cleanups and corrections to PCI-E handling
Date: Thu, 14 Feb 2019 16:08:06 +1100	[thread overview]
Message-ID: <20190214050808.16653-1-david@gibson.dropbear.id.au> (raw)

Here are a couple of cleanups for PCI-E handling which arose out of
some other work I have in progress.  At least the first of these
patches has been posted before as part of a different series, but
wasn't ready to go at the time.

David Gibson (2):
  pci: Simplify pci_bus_is_root()
  pcie: Don't allow extended config space access via conventional PCI
    bridges

 hw/pci-bridge/pci_expander_bridge.c |  6 -----
 hw/pci/pci.c                        | 40 ++++++++++++++++++++++-------
 hw/virtio/virtio-pci.c              |  1 +
 include/hw/pci/pci.h                |  5 ++--
 include/hw/pci/pci_bus.h            | 13 ++++++++++
 5 files changed, 48 insertions(+), 17 deletions(-)

-- 
2.20.1

             reply	other threads:[~2019-02-14  5:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14  5:08 David Gibson [this message]
2019-02-14  5:08 ` [Qemu-devel] [PATCH 1/2] pci: Simplify pci_bus_is_root() David Gibson
2019-02-14  5:08 ` [Qemu-devel] [PATCH 2/2] pcie: Don't allow extended config space access via conventional PCI bridges David Gibson
2019-02-14  6:04   ` Alexey Kardashevskiy
2019-02-15  0:44     ` David Gibson
2019-02-14  5:38 ` [Qemu-devel] [PATCH 0/2] Some small cleanups and corrections to PCI-E handling 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=20190214050808.16653-1-david@gibson.dropbear.id.au \
    --to=david@gibson.dropbear.id.au \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mdroth@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.