From: Keith Busch <kbusch@kernel.org>
To: Zhiping Zhang <zhipingz@meta.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Michael Guralnik <michaelgur@nvidia.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Christian Konig <christian.koenig@amd.com>,
Alex Williamson <alex@shazbot.org>,
Bjorn Helgaas <bhelgaas@google.com>,
kvm@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-pci@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v12 0/4] vfio/dma-buf: add TPH support for peer-to-peer access
Date: Tue, 28 Jul 2026 11:03:19 -0600 [thread overview]
Message-ID: <amjg1x6QuEHtGp4M@kbusch-mbp> (raw)
In-Reply-To: <20260715204008.3911275-1-zhipingz@meta.com>
On Wed, Jul 15, 2026 at 01:39:55PM -0700, Zhiping Zhang wrote:
> This series adds TLP Processing Hints (TPH) support to the VFIO dma-buf
> export path, allowing importing drivers (e.g. mlx5) to use the
> exporter's steering tag when performing peer-to-peer DMA into a
> VFIO-owned device.
Thanks, Zhiping. This looks good to me.
Acked-by: Keith Busch <kbusch@kernel.org>
next prev parent reply other threads:[~2026-07-28 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260715204008.3911275-1-zhipingz@meta.com>
2026-07-16 1:07 ` [PATCH v12 0/4] vfio/dma-buf: add TPH support for peer-to-peer access fengchengwen
2026-07-16 14:47 ` Jason Gunthorpe
2026-07-16 20:10 ` Zhiping Zhang
2026-07-16 20:08 ` Zhiping Zhang
2026-07-17 0:16 ` fengchengwen
[not found] ` <20260715204008.3911275-4-zhipingz@meta.com>
2026-07-17 0:36 ` [PATCH v12 3/4] vfio/pci: implement get_pci_tph and DMA_BUF_TPH feature fengchengwen
[not found] ` <20260715204008.3911275-3-zhipingz@meta.com>
2026-07-17 0:59 ` [PATCH v12 2/4] dma-buf: add optional get_pci_tph() callback fengchengwen
2026-07-28 17:03 ` Keith Busch [this message]
2026-07-29 23:03 ` [PATCH v12 0/4] vfio/dma-buf: add TPH support for peer-to-peer access Alex Williamson
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=amjg1x6QuEHtGp4M@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=alex@shazbot.org \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=kvm@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=michaelgur@nvidia.com \
--cc=sumit.semwal@linaro.org \
--cc=zhipingz@meta.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