All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Chengwen Feng <fengchengwen@huawei.com>
Cc: alex@shazbot.org, jgg@ziepe.ca, wathsala.vithanage@arm.com,
	helgaas@kernel.org, wangzhou1@hisilicon.com,
	wangyushan12@huawei.com, liuyonglong@huawei.com,
	kvm@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 0/5] vfio/pci: Add PCIe TPH support
Date: Thu, 23 Apr 2026 17:59:15 +0300	[thread overview]
Message-ID: <20260423145915.GG172828@unreal> (raw)
In-Reply-To: <20260423010851.46737-1-fengchengwen@huawei.com>

On Thu, Apr 23, 2026 at 09:08:46AM +0800, Chengwen Feng wrote:
> This series adds support for PCIe TLP Processing Hints (TPH) to
> vfio-pci, allowing userspace to manage device steering tags for
> improved performance and QoS in virtualized deployments.
> 
> The implementation follows a clean incremental structure:
> - Patch 1: Export pcie_tph_get_st_modes()
> - Patch 2: Introduce UAPI ABI and implement capability query to
>   let userspace discover supported TPH modes, ST table presence
>   and size. Also add module parameter enable_unsafe_tph_ds to
>   guard unsafe usage of TPH Device-Specific mode with no ST table.
> - Patch 3: Add TPH enable/disable with mode selection. Restrict
>   unsafe Device-Specific mode without ST table to be allowed only
>   when the module parameter is enabled.
> - Patch 4: Add interface to batch get per-CPU steering tags for
>   device-specific mode without standard ST table. This interface
>   is only available when the unsafe module parameter is enabled.
> - Patch 5: Add interface to batch program steering tag table
>   entries for standard TPH modes.
> 
> All user API definitions are finalized in the first patch and
> remain stable across the series. The design follows existing
> VFIO conventions and relies on kernel pcie-tph infrastructure.
> 
> To avoid potential security risks in virtualization environments,
> TPH Device-Specific mode without a standard ST table is blocked
> by default. It can only be enabled by administrators via the
> enable_unsafe_tph_ds module parameter for trusted bare-metal
> userspace.
> 
> This series addresses the TPH management requirements discussed
> in the RFC "Proposal: Add sysfs interface for PCIe TPH Steering
> Tag retrieval and configuration".

As in the RFC, this patch series still lacks an explanation of *why* it is
needed. Please describe the scenario that cannot be handled without these
changes.

Thanks

  parent reply	other threads:[~2026-04-23 14:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  1:08 [PATCH v3 0/5] vfio/pci: Add PCIe TPH support Chengwen Feng
2026-04-23  1:08 ` [PATCH v3 1/5] PCI/TPH: Export pcie_tph_get_st_modes() for external use Chengwen Feng
2026-04-23  1:08 ` [PATCH v3 2/5] vfio/pci: Add PCIe TPH interface with capability query Chengwen Feng
2026-04-23  1:08 ` [PATCH v3 3/5] vfio/pci: Add PCIe TPH enable/disable support Chengwen Feng
2026-04-23  1:08 ` [PATCH v3 4/5] vfio/pci: Add PCIe TPH GET_ST interface Chengwen Feng
2026-04-23  1:08 ` [PATCH v3 5/5] vfio/pci: Add PCIe TPH SET_ST interface Chengwen Feng
2026-04-23 14:59 ` Leon Romanovsky [this message]
2026-04-24  1:25   ` [PATCH v3 0/5] vfio/pci: Add PCIe TPH support fengchengwen
2026-04-24 22:30     ` Jason Gunthorpe
2026-04-30  3:56       ` fengchengwen

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=20260423145915.GG172828@unreal \
    --to=leon@kernel.org \
    --cc=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 \
    /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.