From: Alex Williamson <alex@shazbot.org>
To: Chengwen Feng <fengchengwen@huawei.com>
Cc: <jgg@ziepe.ca>, <helgaas@kernel.org>,
<wathsala.vithanage@arm.com>, <wei.huang2@amd.com>,
<zhipingz@meta.com>, <wangzhou1@hisilicon.com>,
<wangyushan12@huawei.com>, <liuyonglong@huawei.com>,
<kvm@vger.kernel.org>, <linux-pci@vger.kernel.org>,
alex@shazbot.org
Subject: Re: [PATCH v19 16/18] vfio/pci: Implement TPH_ST feature for batch ST table programming
Date: Wed, 8 Jul 2026 17:29:54 -0600 [thread overview]
Message-ID: <20260708172954.14bff5c4@shazbot.org> (raw)
In-Reply-To: <20260702124224.57168-17-fengchengwen@huawei.com>
On Thu, 2 Jul 2026 20:42:22 +0800
Chengwen Feng <fengchengwen@huawei.com> wrote:
> Add vfio_pci_core_feature_tph_st() to implement the SET-only
> VFIO_DEVICE_FEATURE_TPH_ST uAPI for batch TPH ST table programming.
>
> Implement helper routines to calculate ST table size and resolve ST tags
> from multiple sources: NONE, DMABUF, CPU volatile/persistent, and LITERAL.
>
> Batch program contiguous ST table entries according to user inputs, support
> stop-on-zero-ST semantics, and return the number of successfully written
> entries. Hold memory_lock and ensure device is in D0 state during hardware
> operations.
>
> Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
> ---
> drivers/vfio/pci/vfio_pci_core.c | 119 +++++++++++++++++++++++++++++++
> 1 file changed, 119 insertions(+)
>
> diff --git a/drivers/vfio/pci/vfio_pci_core.c b/drivers/vfio/pci/vfio_pci_core.c
> index ed6bbffa8b26..7251e251824a 100644
> --- a/drivers/vfio/pci/vfio_pci_core.c
> +++ b/drivers/vfio/pci/vfio_pci_core.c
> @@ -1713,6 +1713,123 @@ static int vfio_pci_core_feature_tph_resolve(struct vfio_pci_core_device *vdev,
> return copy_to_user(arg, &resolve, sizeof(resolve)) ? -EFAULT : 0;
> }
>
> +static u32 tph_calc_st_size(struct vfio_pci_core_device *vdev)
> +{
> + struct pci_dev *pdev = vdev->pdev;
> + u32 loc = pcie_tph_get_st_table_loc(pdev);
> + int ret;
> +
> + if (loc == PCI_TPH_LOC_CAP) {
> + return pcie_tph_get_st_table_size(pdev);
> + } else if (loc == PCI_TPH_LOC_MSIX) {
> + ret = pci_msix_vec_count(pdev);
> + if (ret < 0)
> + return 0;
> + return ret;
> + } else {
> + return 0;
> + }
> +}
> +
> +static int tph_get_st_tag(struct pci_dev *pdev, u32 src_bits, u32 src_hndl,
> + bool extended, u16 *tag)
> +{
> + int ret = 0;
> + u8 ph;
> +
> + if (src_bits & VFIO_DEVICE_TPH_SRC_NONE)
> + *tag = 0;
> + else if (src_bits & VFIO_DEVICE_TPH_SRC_DMABUF)
> + ret = vfio_pci_dma_buf_get_tph_by_fd(src_hndl, extended,
> + tag, &ph);
> + else if (src_bits & VFIO_DEVICE_TPH_SRC_CPU_VOLATILE)
> + ret = pcie_tph_get_cpu_st_explicit(pdev, TPH_MEM_TYPE_VM,
> + extended, src_hndl, tag);
> + else if (src_bits & VFIO_DEVICE_TPH_SRC_CPU_PERSISTENT)
> + ret = pcie_tph_get_cpu_st_explicit(pdev, TPH_MEM_TYPE_PM,
> + extended, src_hndl, tag);
> + else if (src_bits & VFIO_DEVICE_TPH_SRC_LITERAL)
> + *tag = src_hndl;
> +
> + if (ret != 0)
> + *tag = 0;
> +
> + return ret;
> +}
> +
> +static int vfio_pci_core_feature_tph_st(struct vfio_pci_core_device *vdev,
> + u32 flags,
> + struct vfio_device_feature_tph_st __user *arg,
> + size_t argsz)
> +{
> + u32 permit_flags = VFIO_DEVICE_TPH_SRC_MASK | VFIO_DEVICE_TPH_EXTENDED;
> + struct vfio_device_feature_tph_st tph_st = {0};
> + struct pci_dev *pdev = vdev->pdev;
> + u32 src_bits, st_size;
> + bool stop_on_zero_st;
> + u32 *src_hndl = NULL;
> + void __user *uptr;
> + bool extended;
> + int ret, i;
> + u16 tag;
> +
> + if (!vdev->tph_permit || vdev->tph_policy == VFIO_PCI_TPH_POLICY_NO_ST)
> + return -EOPNOTSUPP;
> +
> + ret = vfio_check_feature(flags, argsz, VFIO_DEVICE_FEATURE_SET,
> + sizeof(tph_st));
> + if (ret <= 0)
> + return ret;
Again, not how vfio_check_feature() convetion.
> +
> + if (copy_from_user(&tph_st, arg, sizeof(tph_st)))
> + return -EFAULT;
> +
MUST validate undefined flags are zero.
> + src_bits = tph_st.flags & VFIO_DEVICE_TPH_SRC_MASK;
> + if (vdev->tph_policy != VFIO_PCI_TPH_POLICY_LITERAL)
> + permit_flags &= ~VFIO_DEVICE_TPH_SRC_LITERAL;
> + if (!(tph_st.flags & permit_flags) || !is_power_of_2(src_bits))
> + return -EINVAL;
> + extended = !!(tph_st.flags & VFIO_DEVICE_TPH_EXTENDED);
> + if (extended && !pcie_tph_supported(vdev->pdev, true))
> + return -EINVAL;
> +
> + st_size = tph_calc_st_size(vdev);
> + if (tph_st.start >= st_size || tph_st.count > st_size - tph_st.start ||
> + tph_st.count == 0)
> + return -EINVAL;
> +
> + uptr = u64_to_user_ptr(tph_st.dests);
> + if (!(src_bits & VFIO_DEVICE_TPH_SRC_NONE)) {
> + src_hndl = memdup_array_user(uptr, tph_st.count, sizeof(u32));
> + if (IS_ERR(src_hndl))
> + return PTR_ERR(src_hndl);
> + }
> +
> + down_write(&vdev->memory_lock);
No, vfio_pci_memory_lock_and_enable().
> + ret = vfio_pci_set_power_state(vdev, PCI_D0);
No, PM runtime get/set, but once again it's already done in the call
path.
> + if (ret)
> + goto out;
> +
> + stop_on_zero_st = !!(tph_st.flags & VFIO_DEVICE_TPH_REQUIRE_ST);
> + if (tph_st.flags & VFIO_DEVICE_TPH_SRC_NONE)
> + stop_on_zero_st = false;
> + for (i = 0; i < tph_st.count; i++) {
> + ret = tph_get_st_tag(pdev, src_bits, src_hndl ? src_hndl[i] : 0,
> + extended, &tag);
> + if (ret || (stop_on_zero_st && tag == 0))
> + break;
Missing bounds check on tag if !extended.
In IV mode, don't we need to know the vector is enabled?
> + ret = pcie_tph_set_st_entry(pdev, tph_st.start + i, tag);
We're defeating the entire reason we created a batching interface by
not also implementing a batching interface in the PCI/TPH code. This
does a disable before each set. Thanks,
Alex
> + if (ret)
> + break;
> + }
> + ret = i;
> +
> +out:
> + up_write(&vdev->memory_lock);
> + kfree(src_hndl);
> + return ret;
> +}
> +
> int vfio_pci_core_ioctl_feature(struct vfio_device *device, u32 flags,
> void __user *arg, size_t argsz)
> {
> @@ -1736,6 +1853,8 @@ int vfio_pci_core_ioctl_feature(struct vfio_device *device, u32 flags,
> case VFIO_DEVICE_FEATURE_TPH_RESOLVE:
> return vfio_pci_core_feature_tph_resolve(vdev, flags,
> arg, argsz);
> + case VFIO_DEVICE_FEATURE_TPH_ST:
> + return vfio_pci_core_feature_tph_st(vdev, flags, arg, argsz);
> default:
> return -ENOTTY;
> }
next prev parent reply other threads:[~2026-07-08 23:34 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 12:42 [PATCH v19 00/18] vfio/pci: Add PCIe TPH support Chengwen Feng
2026-07-02 12:42 ` [PATCH v19 01/18] PCI/TPH: Fix pcie_tph_get_st_table_loc() field extraction Chengwen Feng
2026-07-02 12:51 ` sashiko-bot
2026-07-02 12:42 ` [PATCH v19 02/18] PCI/TPH: Fix tph_enabled concurrent update race by bitfield packing Chengwen Feng
2026-07-02 12:51 ` sashiko-bot
2026-07-02 12:42 ` [PATCH v19 03/18] PCI/TPH: Cache TPH requester capability at probe time Chengwen Feng
2026-07-02 12:55 ` sashiko-bot
2026-07-02 12:42 ` [PATCH v19 04/18] PCI/TPH: Refactor pcie_enable_tph & add explicit requester variant Chengwen Feng
2026-07-02 12:50 ` sashiko-bot
2026-07-08 23:33 ` Alex Williamson
2026-07-09 9:22 ` fengchengwen
2026-07-13 0:21 ` fengchengwen
2026-07-02 12:42 ` [PATCH v19 05/18] PCI/TPH: Refactor pcie_tph_get_cpu_st & add explicit variant Chengwen Feng
2026-07-02 12:56 ` sashiko-bot
2026-07-02 12:42 ` [PATCH v19 06/18] PCI/TPH: Expose the enabled TPH requester type Chengwen Feng
2026-07-02 12:49 ` sashiko-bot
2026-07-08 23:33 ` Alex Williamson
2026-07-09 9:30 ` fengchengwen
2026-07-02 12:42 ` [PATCH v19 07/18] PCI/TPH: Add pcie_tph_supported() helper to check TPH capability attributes Chengwen Feng
2026-07-02 12:53 ` sashiko-bot
2026-07-03 0:39 ` fengchengwen
2026-07-08 23:32 ` Alex Williamson
2026-07-09 9:36 ` fengchengwen
2026-07-02 12:42 ` [PATCH v19 08/18] PCI/TPH: Add pci_tph_dsm_supported() helper to detect device TPH ST _DSM Chengwen Feng
2026-07-02 12:55 ` sashiko-bot
2026-07-02 12:42 ` [PATCH v19 09/18] vfio/pci: Hide TPH capability when TPH is unsupported Chengwen Feng
2026-07-02 13:00 ` sashiko-bot
2026-07-03 0:36 ` fengchengwen
2026-07-08 23:32 ` Alex Williamson
2026-07-09 11:00 ` fengchengwen
2026-07-02 12:42 ` [PATCH v19 10/18] vfio/pci: Introduce tph policy parameter for staged TPH feature enablement Chengwen Feng
2026-07-02 12:50 ` sashiko-bot
2026-07-08 23:31 ` Alex Williamson
2026-07-09 11:29 ` fengchengwen
2026-07-02 12:42 ` [PATCH v19 11/18] vfio/pci: Virtualize PCIe TPH capability registers Chengwen Feng
2026-07-02 13:04 ` sashiko-bot
2026-07-03 0:51 ` fengchengwen
2026-07-08 23:31 ` Alex Williamson
2026-07-09 11:40 ` fengchengwen
2026-07-02 12:42 ` [PATCH v19 12/18] vfio/pci: Add dmabuf TPH metadata storage and fd query helper Chengwen Feng
2026-07-02 12:56 ` sashiko-bot
2026-07-03 0:53 ` fengchengwen
2026-07-08 23:31 ` Alex Williamson
2026-07-09 11:49 ` fengchengwen
2026-07-09 18:50 ` Alex Williamson
2026-07-14 10:46 ` fengchengwen
2026-07-14 13:57 ` Alex Williamson
2026-07-02 12:42 ` [PATCH v19 13/18] vfio/pci: Introduce VFIO_DEVICE_FEATURE_TPH family uapi for PCI TPH control Chengwen Feng
2026-07-02 13:01 ` sashiko-bot
2026-07-03 0:57 ` fengchengwen
2026-07-08 23:31 ` Alex Williamson
2026-07-09 11:56 ` fengchengwen
2026-07-02 12:42 ` [PATCH v19 14/18] vfio/pci: Implement VFIO_DEVICE_FEATURE_TPH and valid TPH config write support Chengwen Feng
2026-07-02 13:04 ` sashiko-bot
2026-07-03 1:16 ` fengchengwen
2026-07-08 23:30 ` Alex Williamson
2026-07-09 12:16 ` fengchengwen
2026-07-02 12:42 ` [PATCH v19 15/18] vfio/pci: Implement TPH_RESOLVE feature for DMABUF and CPU source resolving Chengwen Feng
2026-07-02 13:00 ` sashiko-bot
2026-07-03 1:26 ` fengchengwen
2026-07-08 23:31 ` Alex Williamson
2026-07-09 12:20 ` fengchengwen
2026-07-02 12:42 ` [PATCH v19 16/18] vfio/pci: Implement TPH_ST feature for batch ST table programming Chengwen Feng
2026-07-02 13:04 ` sashiko-bot
2026-07-03 1:42 ` fengchengwen
2026-07-08 23:29 ` Alex Williamson [this message]
2026-07-09 12:36 ` fengchengwen
2026-07-09 13:49 ` Alex Williamson
2026-07-02 12:42 ` [PATCH v19 17/18] vfio/pci: Reset hardware TPH state on device enable/disable Chengwen Feng
2026-07-02 13:00 ` sashiko-bot
2026-07-08 23:29 ` Alex Williamson
2026-07-09 12:39 ` fengchengwen
2026-07-02 12:42 ` [PATCH v19 18/18] vfio/pci: Expose tph_policy via debugfs Chengwen Feng
2026-07-02 12:59 ` sashiko-bot
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=20260708172954.14bff5c4@shazbot.org \
--to=alex@shazbot.org \
--cc=fengchengwen@huawei.com \
--cc=helgaas@kernel.org \
--cc=jgg@ziepe.ca \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=wangyushan12@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=wathsala.vithanage@arm.com \
--cc=wei.huang2@amd.com \
--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 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.