From: Jason Gunthorpe <jgg@ziepe.ca>
To: Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
nd <nd@arm.com>, Philipp Stanner <pstanner@redhat.com>,
Yunxiang Li <Yunxiang.Li@amd.com>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
Ankit Agrawal <ankita@nvidia.com>,
"open list:VFIO DRIVER" <kvm@vger.kernel.org>,
Dhruv Tripathi <Dhruv.Tripathi@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Jeremy Linton <Jeremy.Linton@arm.com>
Subject: Re: [RFC PATCH] vfio/pci: add PCIe TPH to device feature ioctl
Date: Tue, 1 Apr 2025 20:52:25 -0300 [thread overview]
Message-ID: <20250401235225.GA327284@ziepe.ca> (raw)
In-Reply-To: <PAWPR08MB8909781BE207255E830DE1589FAC2@PAWPR08MB8909.eurprd08.prod.outlook.com>
On Tue, Apr 01, 2025 at 11:38:01PM +0000, Wathsala Wathawana Vithanage wrote:
> > Really we can't block device specific mode anyhow because we can't even
> > discover it on the kernel side..
>
> We cannot block users from writing a steering-tag to a device specific location, but
> can we use a capability to prevent users from enabling device specific mode on the device?
qemu could do that, but the vfio kernel side really shouldn't.. There
is no reason vfio userspace on bare metal couldn't use device specific
mode.
Jason
next prev parent reply other threads:[~2025-04-01 23:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 22:46 Wathsala Vithanage
2025-02-28 18:48 ` Alex Williamson
2025-03-03 4:20 ` Wathsala Wathawana Vithanage
2025-03-04 3:12 ` Alex Williamson
2025-03-04 7:01 ` Wathsala Wathawana Vithanage
2025-04-26 12:49 ` Wathsala Wathawana Vithanage
2025-03-03 7:49 ` Philipp Stanner
2025-03-03 17:21 ` Wathsala Wathawana Vithanage
2025-03-04 14:14 ` Jason Gunthorpe
2025-03-04 22:38 ` Wathsala Wathawana Vithanage
2025-03-05 1:24 ` Alex Williamson
2025-03-05 6:11 ` Wathsala Wathawana Vithanage
2025-03-05 18:58 ` Jason Gunthorpe
2025-03-05 20:21 ` Wathsala Wathawana Vithanage
2025-03-12 7:53 ` Tian, Kevin
2025-03-14 1:49 ` Wathsala Wathawana Vithanage
2025-04-07 5:16 ` Tian, Kevin
2025-04-01 14:11 ` Jason Gunthorpe
2025-04-01 23:38 ` Wathsala Wathawana Vithanage
2025-04-01 23:52 ` Jason Gunthorpe [this message]
2025-04-07 5:22 ` Tian, Kevin
2025-04-26 12:42 ` Wathsala Wathawana Vithanage
2025-06-02 23:06 ` [RFC PATCH v2 0/1] VFIO ioctl for TLP Processing Hints Wathsala Vithanage
2025-06-02 23:06 ` [RFC PATCH v2 1/1] vfio/pci: add PCIe TPH device ioctl Wathsala Vithanage
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=20250401235225.GA327284@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Dhruv.Tripathi@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Jeremy.Linton@arm.com \
--cc=Yunxiang.Li@amd.com \
--cc=alex.williamson@redhat.com \
--cc=ankita@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=nd@arm.com \
--cc=pstanner@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®