From: Jason Gunthorpe <jgg@nvidia.com>
To: fengchengwen <fengchengwen@huawei.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com
Subject: Re: [RFC] Proposal: Add sysfs interface for PCIe TPH Steering Tag retrieval and configuration
Date: Tue, 14 Apr 2026 12:08:12 -0300 [thread overview]
Message-ID: <20260414150812.GI2588311@nvidia.com> (raw)
In-Reply-To: <284350ea-e398-12da-c3e2-e156a1e6d127@huawei.com>
On Tue, Apr 14, 2026 at 10:40:39PM +0800, fengchengwen wrote:
> On 2026/4/14 19:57, Jason Gunthorpe wrote:
>
> On Tue, Apr 14, 2026 at 09:33:01AM +0800, fengchengwen wrote:
>
>
> - For devices using the spec-defined ST location, userspace may
> provide (index, cpu) associations for the kernel to program safely.
>
> No, it is not safe.
>
> Thank you for your clarification and for emphasizing the security
> concern.
>
> To address this properly and ensure safety, I plan to add a dedicated
> kernel boot parameter, similar to iommu.passthrough, to control this
> interface. The behavior would be:
No, that's nonsense. The driver owns the tph table, nothing else is
allowed to manipulate it.
You haven't even sensibly explained why you'd want this.
Jason
prev parent reply other threads:[~2026-04-14 15:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 14:30 [RFC] Proposal: Add sysfs interface for PCIe TPH Steering Tag retrieval and configuration fengchengwen
2026-04-13 10:01 ` 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
2026-04-14 14:46 ` fengchengwen
2026-04-14 15:11 ` Jason Gunthorpe
2026-04-15 1:47 ` fengchengwen
2026-04-13 13:35 ` Jason Gunthorpe
2026-04-14 1:33 ` fengchengwen
2026-04-14 11:57 ` Jason Gunthorpe
[not found] ` <284350ea-e398-12da-c3e2-e156a1e6d127@huawei.com>
2026-04-14 15:08 ` Jason Gunthorpe [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=20260414150812.GI2588311@nvidia.com \
--to=jgg@nvidia.com \
--cc=bhelgaas@google.com \
--cc=fengchengwen@huawei.com \
--cc=linux-pci@vger.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 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.