From: Leon Romanovsky <leon@kernel.org>
To: "Bjorn Helgaas" <bhelgaas@google.com>,
"Logan Gunthorpe" <logang@deltatee.com>,
"Chaitanya Kulkarni" <kch@nvidia.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jens Axboe" <axboe@kernel.dk>,
"Alex Williamson" <alex@shazbot.org>,
"Leon Romanovsky" <leon@kernel.org>,
"Ankit Agrawal" <ankita@nvidia.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Joerg Roedel (AMD)" <joro@8bytes.org>,
"Will Deacon" <will@kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, iommu@lists.linux.dev,
Tushar Dave <tdave@nvidia.com>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-rdma@vger.kernel.org,
kvm@vger.kernel.org
Subject: [PATCH v7 16/19] dma-buf: Let importers ask how peer-to-peer traffic is routed
Date: Sun, 20 Sep 2026 14:41:28 +0300 [thread overview]
Message-ID: <20260920-fix-p2p-acs-v4-0-v7-16-ca0828ab697c@nvidia.com> (raw)
In-Reply-To: <20260920-fix-p2p-acs-v4-0-v7-0-ca0828ab697c@nvidia.com>
From: Leon Romanovsky <leonro@nvidia.com>
Exporters keep the &struct p2pdma_provider backing a buffer in their own
private data. An importer cannot reach it, so it has no way to learn how
its own peer-to-peer traffic would be routed before it programs its
hardware.
Add an optional @p2pdma_provider callback for an exporter to hand that
provider out, and dma_buf_p2pdma_map_type() for an importer to ask by TLP
class. Exporters keep the provider where it already lives, so this adds an
operation rather than changing any existing signature or structure.
Tested-by: Tushar Dave <tdave@nvidia.com>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
---
drivers/dma-buf/dma-buf-mapping.c | 39 +++++++++++++++++++++++++++++++++++++++
include/linux/dma-buf-mapping.h | 3 +++
include/linux/dma-buf.h | 19 +++++++++++++++++++
3 files changed, 61 insertions(+)
diff --git a/drivers/dma-buf/dma-buf-mapping.c b/drivers/dma-buf/dma-buf-mapping.c
index 794acff2546a..41702045f803 100644
--- a/drivers/dma-buf/dma-buf-mapping.c
+++ b/drivers/dma-buf/dma-buf-mapping.c
@@ -6,6 +6,45 @@
#include <linux/dma-buf-mapping.h>
#include <linux/dma-resv.h>
+/**
+ * dma_buf_p2pdma_map_type - How peer-to-peer traffic to a buffer is routed
+ * @attach: attachment of the importer that will issue the traffic
+ * @tlp_flags: &enum pci_p2pdma_tlp_flags describing the TLPs it will issue
+ *
+ * Reports how the PCIe fabric routes @tlp_flags traffic between the buffer
+ * behind @attach and the importer attached to it, so that an importer can
+ * choose the TLP attributes that earn it a direct route before it programs
+ * its hardware.
+ *
+ * The caller must hold the reservation lock. The provider is owned by the
+ * exporter's driver binding, and exporters revoke under that lock before
+ * letting an unbind proceed, so dropping it any earlier would leave this
+ * racing a teardown that frees the provider.
+ *
+ * Return: the mapping type for @tlp_flags traffic, or PCI_P2PDMA_MAP_NONE
+ * when the exporter names no &struct p2pdma_provider and nothing is known
+ * about the route.
+ */
+enum pci_p2pdma_map_type
+dma_buf_p2pdma_map_type(struct dma_buf_attachment *attach,
+ unsigned int tlp_flags)
+{
+ struct dma_buf *dmabuf = attach->dmabuf;
+ struct p2pdma_provider *provider;
+
+ dma_resv_assert_held(dmabuf->resv);
+
+ if (!dmabuf->ops->p2pdma_provider)
+ return PCI_P2PDMA_MAP_NONE;
+
+ provider = dmabuf->ops->p2pdma_provider(dmabuf);
+ if (!provider)
+ return PCI_P2PDMA_MAP_NONE;
+
+ return pci_p2pdma_map_type_tlp(provider, attach->dev, tlp_flags);
+}
+EXPORT_SYMBOL_NS_GPL(dma_buf_p2pdma_map_type, "DMA_BUF");
+
static struct scatterlist *fill_sg_entry(struct scatterlist *sgl, size_t length,
dma_addr_t addr)
{
diff --git a/include/linux/dma-buf-mapping.h b/include/linux/dma-buf-mapping.h
index 09bde3f748e4..37b3da10b17a 100644
--- a/include/linux/dma-buf-mapping.h
+++ b/include/linux/dma-buf-mapping.h
@@ -7,6 +7,9 @@
#define __DMA_BUF_MAPPING_H__
#include <linux/dma-buf.h>
+enum pci_p2pdma_map_type
+dma_buf_p2pdma_map_type(struct dma_buf_attachment *attach,
+ unsigned int tlp_flags);
struct sg_table *dma_buf_phys_vec_to_sgt(struct dma_buf_attachment *attach,
struct p2pdma_provider *provider,
struct phys_vec *phys_vec,
diff --git a/include/linux/dma-buf.h b/include/linux/dma-buf.h
index d1203da56fc5..d56a48d41215 100644
--- a/include/linux/dma-buf.h
+++ b/include/linux/dma-buf.h
@@ -186,6 +186,25 @@ struct dma_buf_ops {
* if the call would block.
*/
+ /**
+ * @p2pdma_provider:
+ *
+ * Returns the &struct p2pdma_provider backing this buffer, so that an
+ * importer can ask how its peer-to-peer traffic would be routed before
+ * it programs its hardware. Importers reach this through
+ * dma_buf_p2pdma_map_type() rather than calling it directly.
+ *
+ * Exporters of MMIO memory that is reachable peer-to-peer should
+ * implement this. Called with the &dma_buf.resv reservation lock held,
+ * which is what lets an exporter refuse once it has revoked the buffer
+ * and started tearing the provider down. This callback is optional.
+ *
+ * Returns:
+ *
+ * The provider backing the buffer.
+ */
+ struct p2pdma_provider *(*p2pdma_provider)(struct dma_buf *dmabuf);
+
/**
* @release:
*
--
2.55.0
next prev parent reply other threads:[~2026-09-20 11:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 11:41 [PATCH v7 00/19] PCI/P2PDMA: Route peer-to-peer DMA by TLP class Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 01/19] PCI/P2PDMA: Document the TLP attribute assumptions Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 02/19] PCI/P2PDMA: Derive routing from directional ACS controls Leon Romanovsky
2026-09-21 20:05 ` Logan Gunthorpe
2026-09-20 11:41 ` [PATCH v7 03/19] PCI: Reject unreadable ACS controls in isolation checks Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 04/19] PCI/P2PDMA: Evaluate ACS controls at the path divergence Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 05/19] PCI/P2PDMA: Document directional ACS routing Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 06/19] PCI/P2PDMA: Collect the path's ACS controls before deciding Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 07/19] PCI/P2PDMA: Answer routing per TLP class Leon Romanovsky
2026-09-21 20:20 ` Logan Gunthorpe
2026-09-20 11:41 ` [PATCH v7 08/19] PCI/P2PDMA: Route Relaxed Ordering Completions directly Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 09/19] PCI/P2PDMA: Reject Translated Requests blocked by Translation Blocking Leon Romanovsky
2026-09-21 20:38 ` Logan Gunthorpe
2026-09-20 11:41 ` [PATCH v7 10/19] PCI/P2PDMA: Route Translated Requests under Direct Translated P2P Leon Romanovsky
2026-09-21 20:51 ` Logan Gunthorpe
2026-09-20 11:41 ` [PATCH v7 11/19] PCI/P2PDMA: Log detailed ACS routing diagnostics Leon Romanovsky
2026-09-21 21:19 ` Logan Gunthorpe
2026-09-20 11:41 ` [PATCH v7 12/19] PCI/P2PDMA: Add KUnit tests for the ACS routing decisions Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 13/19] PCI/P2PDMA: Test the ACS P2P routing walk Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 14/19] PCI: Add KUnit coverage for ACS isolation checks Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 15/19] PCI/P2PDMA: Document TLP-class routing Leon Romanovsky
2026-09-21 22:16 ` Logan Gunthorpe
2026-09-22 9:27 ` Leon Romanovsky
2026-09-22 15:43 ` Logan Gunthorpe
2026-09-20 11:41 ` Leon Romanovsky [this message]
2026-09-20 11:41 ` [PATCH v7 17/19] vfio/pci: Hand out the P2PDMA provider behind a dma-buf Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 18/19] RDMA/uverbs: " Leon Romanovsky
2026-09-20 11:41 ` [PATCH v7 19/19] RDMA/mlx5: Ask P2PDMA whether ATS takes a direct peer-to-peer route Leon Romanovsky
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=20260920-fix-p2p-acs-v4-0-v7-16-ca0828ab697c@nvidia.com \
--to=leon@kernel.org \
--cc=alex@shazbot.org \
--cc=ankita@nvidia.com \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kch@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=skhan@linuxfoundation.org \
--cc=sumit.semwal@linaro.org \
--cc=tdave@nvidia.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®