From: Bjorn Helgaas <helgaas@kernel.org>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: "linux-pci @ vger . kernel . org" <linux-pci@vger.kernel.org>,
linux-kernel@vger.kernel.org,
"Christian König" <christian.koenig@amd.com>,
"Christoph Hellwig" <hch@lst.de>
Subject: Re: [PATCH v2] PCI/P2PDMA: Root complex whitelist should not apply when an IOMMU is present
Date: Wed, 19 Jun 2019 16:45:02 -0500 [thread overview]
Message-ID: <20190619214502.GE143205@google.com> (raw)
In-Reply-To: <20190619185626.15806-1-logang@deltatee.com>
On Wed, Jun 19, 2019 at 12:56:26PM -0600, Logan Gunthorpe wrote:
> Presently, there is no path to DMA map P2PDMA memory, so if a TLP
> targeting this memory hits the root complex and an IOMMU is present,
> the IOMMU will reject the transaction, even if the RC would support
> P2PDMA.
>
> So until the kernel knows to map these DMA addresses in the IOMMU,
> we should not enable the whitelist when an IOMMU is present.
>
> Link: https://lore.kernel.org/linux-pci/20190522201252.2997-1-logang@deltatee.com/
> Fixes: 0f97da831026 ("PCI/P2PDMA: Allow P2P DMA between any devices under AMD ZEN Root Complex")
> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
> Reviewed-by: Christian König <christian.koenig@amd.com>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: Christoph Hellwig <hch@lst.de>
Applied to for-linus for v5.2, since we merged 0f97da831026 during the v5.2
merge window, thanks!
> ---
> drivers/pci/p2pdma.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
> index a98126ad9c3a..a4994aa3acc0 100644
> --- a/drivers/pci/p2pdma.c
> +++ b/drivers/pci/p2pdma.c
> @@ -18,6 +18,7 @@
> #include <linux/percpu-refcount.h>
> #include <linux/random.h>
> #include <linux/seq_buf.h>
> +#include <linux/iommu.h>
>
> struct pci_p2pdma {
> struct gen_pool *pool;
> @@ -299,6 +300,9 @@ static bool root_complex_whitelist(struct pci_dev *dev)
> struct pci_dev *root = pci_get_slot(host->bus, PCI_DEVFN(0, 0));
> unsigned short vendor, device;
>
> + if (iommu_present(dev->dev.bus))
> + return false;
> +
> if (!root)
> return false;
>
> --
> 2.20.1
>
prev parent reply other threads:[~2019-06-19 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 18:56 [PATCH v2] PCI/P2PDMA: Root complex whitelist should not apply when an IOMMU is present Logan Gunthorpe
2019-06-19 21:45 ` Bjorn Helgaas [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=20190619214502.GE143205@google.com \
--to=helgaas@kernel.org \
--cc=christian.koenig@amd.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
/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).