From: fengchengwen <fengchengwen@huawei.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Leon Romanovsky <leon@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>, <linux-rdma@vger.kernel.org>,
<linux-pci@vger.kernel.org>, <netdev@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
Keith Busch <kbusch@kernel.org>, Yochai Cohen <yochai@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>,
Zhiping Zhang <zhipingz@meta.com>
Subject: Re: [RFC] Proposal: Add sysfs interface for PCIe TPH Steering Tag retrieval and configuration
Date: Wed, 15 Apr 2026 09:47:43 +0800 [thread overview]
Message-ID: <9a7609b7-1d8d-4758-8f3b-081658d90711@huawei.com> (raw)
In-Reply-To: <20260414151125.GF2577880@ziepe.ca>
On 4/14/2026 11:11 PM, Jason Gunthorpe wrote:
> On Tue, Apr 14, 2026 at 10:46:00PM +0800, fengchengwen wrote:
>> We have a real platform requirement:
>>
>> * 1. Devices in TPH Device-Specific Mode with no standard ST table
>> * 2. Steering Tags must be obtained from ACPI _DSM (kernel-only)
>> * 3. Devices are fully managed by userspace drivers (VFIO/UIO)
>> * 4. Userspace must program STs into vendor-specific registers
>
> No, this is nonsenscial too.
>
> If you want to control the steering tags for MMIO BAR memory exposed
> by VFIO then the DMABUF mechanism Keith & co has been working on is
> the correct approach.
>
> If the VFIO user needs to control steering tags for the device it is
> directly controling then it must do that through VFIO ioctls.
>
> Nobody messes around with other devices under the covers of the
> operating kernel driver. Stop proposing that.
Understood.
For VFIO-passed devices that are fully under userspace control,
we will implement the TPH Steering Tag query interface
exclusively through VFIO ioctls, not sysfs.
This will allow userspace to query per-CPU Steering Tags
from platform firmware (ACPI _DSM) for the VFIO device,
which is fully under its control.
Thanks
>
> Jason
prev parent reply other threads:[~2026-04-15 1:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6ea4c4c2-774e-aa76-3665-918e2a24cc84@huawei.com>
2026-04-13 10:01 ` [RFC] Proposal: Add sysfs interface for PCIe TPH Steering Tag retrieval and configuration Leon Romanovsky
2026-04-13 12:04 ` fengchengwen
2026-04-13 19:19 ` Leon Romanovsky
2026-04-14 1:07 ` fengchengwen
2026-04-14 8:57 ` Leon Romanovsky
2026-04-14 9:30 ` fengchengwen
2026-04-14 10:35 ` Leon Romanovsky
[not found] ` <11eaea26-ec10-264a-db1e-951f6b46078d@huawei.com>
2026-04-14 15:11 ` Jason Gunthorpe
2026-04-15 1:47 ` fengchengwen [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=9a7609b7-1d8d-4758-8f3b-081658d90711@huawei.com \
--to=fengchengwen@huawei.com \
--cc=bhelgaas@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=kbusch@kernel.org \
--cc=leon@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yishaih@nvidia.com \
--cc=yochai@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox