From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] pci: Fix pci_device_iommu_address_space() bus propagation
Date: Mon, 17 Aug 2015 19:39:14 +1000 [thread overview]
Message-ID: <1439804354.2416.10.camel@kernel.crashing.org> (raw)
In-Reply-To: <1436051955.3948.29.camel@kernel.crashing.org>
On Sun, 2015-07-05 at 09:19 +1000, Benjamin Herrenschmidt wrote:
> he current code walks up the bus tree for an iommu, however it passes
> to the iommu_fn() callback the bus/devfn of the immediate child of
> the level where the callback was found, rather than the original
> bus/devfn where the search started from.
Hi Michael ! Any comment on this ? I'd like to post my series for "bare
metal" power8 support and the iommu implementation relies on this to
work.
> This prevents iommu's like POWER8 (and in fact also Q35) to properly
> provide an address space for a subset of devices that aren't
> immediate
> children of the iommu.
>
> PCIe carries the originator bdfn acccross to the iommu on all DMA
> transactions, so we must be able to properly identify devices at all
> levels.
>
> This changes the function pci_device_iommu_address_space() to pass
> the original pointers to the iommu_fn() callback instead.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
> With this, I can implement PHB3's (POWER8) iommu properly, I haven't
> submitted the P8 native patch series yet but if you are curious, you
> can look there:
>
> https://github.com/ozbenh/qemu
>
> And more specifically:
>
> https://github.com/ozbenh/qemu/commit/67fe0460c75417908a2b54426cb54fe
> 5a1299a13
>
> For the PHB3 code.
>
> hw/pci/pci.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/hw/pci/pci.c b/hw/pci/pci.c
> index 29f0b0f..8185bbc 100644
> --- a/hw/pci/pci.c
> +++ b/hw/pci/pci.c
> @@ -2403,17 +2403,14 @@ static void pci_device_class_init(ObjectClass
> *klass, void *data)
> AddressSpace *pci_device_iommu_address_space(PCIDevice *dev)
> {
> PCIBus *bus = PCI_BUS(dev->bus);
> + PCIBus *iommu_bus = bus;
>
> - if (bus->iommu_fn) {
> - return bus->iommu_fn(bus, bus->iommu_opaque, dev->devfn);
> + while(iommu_bus && !iommu_bus->iommu_fn && iommu_bus
> ->parent_dev) {
> + iommu_bus = PCI_BUS(iommu_bus->parent_dev->bus);
> }
> -
> - if (bus->parent_dev) {
> - /** We are ignoring the bus master DMA bit of the bridge
> - * as it would complicate things such as VFIO for no good
> reason */
> - return pci_device_iommu_address_space(bus->parent_dev);
> + if (iommu_bus && iommu_bus->iommu_fn) {
> + return iommu_bus->iommu_fn(bus, iommu_bus->iommu_opaque, dev
> ->devfn);
> }
> -
> return &address_space_memory;
> }
>
>
next prev parent reply other threads:[~2015-08-17 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 23:19 [Qemu-devel] [PATCH] pci: Fix pci_device_iommu_address_space() bus propagation Benjamin Herrenschmidt
2015-08-17 9:39 ` Benjamin Herrenschmidt [this message]
2015-08-17 18:50 ` Michael S. Tsirkin
2015-08-17 21:12 ` Benjamin Herrenschmidt
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=1439804354.2416.10.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--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).