From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Liu, Yi L" <yi.l.liu@intel.com>,
Nicolin Chen <nicolinc@nvidia.com>,
"Lu, Baolu" <baolu.lu@intel.com>
Subject: Re: vPASID capability for VF
Date: Tue, 9 May 2023 21:59:13 -0300 [thread overview]
Message-ID: <ZFrsYZPRpHqVyjcZ@nvidia.com> (raw)
In-Reply-To: <20230509183111.6a4a7f39.alex.williamson@redhat.com>
On Tue, May 09, 2023 at 06:31:11PM -0600, Alex Williamson wrote:
> IIRC we originally needed to enable this for a Broadcom NIC that
> stuffed device specific registers in un-architected config space. The
> capabilities we're {un}hiding are architected things that we know are
> unsupported or unsafe, the gaps, just like device specific
> capabilities, we're obliged to expose for functionality. Thanks,
I still think that if people want to do this they should wrap their
stuff in a dvsec..
If we have no choice but to inject a PASID cap for this to work then I
don't think we should quirk every device, but punish those that don't
use DVSEC/etc
So.. If PASID injection is needed then block the unmanaged space and
add quirks for devices that really need it. Otherwise leave it
alone.
Jason
next prev parent reply other threads:[~2023-05-10 0:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 8:34 vPASID capability for VF Tian, Kevin
2023-05-09 22:43 ` Jason Gunthorpe
2023-05-09 22:57 ` Tian, Kevin
2023-05-09 23:13 ` Jason Gunthorpe
2023-05-09 23:41 ` Tian, Kevin
2023-05-10 0:31 ` Alex Williamson
2023-05-10 0:59 ` Jason Gunthorpe [this message]
2023-05-10 2:16 ` Tian, Kevin
2023-05-10 20:39 ` Jason Gunthorpe
2023-05-11 7:42 ` Tian, Kevin
2023-05-10 17:24 ` Alex Williamson
2023-05-10 20:15 ` Jason Gunthorpe
2023-05-11 7:27 ` Tian, Kevin
2023-05-11 11:34 ` Baolu Lu
2023-05-12 2:59 ` Tian, Kevin
2023-05-12 21:01 ` Jason Gunthorpe
2023-05-17 5:09 ` Tian, Kevin
2023-05-11 15:45 ` Alex Williamson
2023-05-12 2:52 ` Tian, Kevin
2023-05-17 5:22 ` Tian, Kevin
2023-07-27 1:17 ` Tian, Kevin
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=ZFrsYZPRpHqVyjcZ@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=baolu.lu@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=yi.l.liu@intel.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