From: Jason Gunthorpe <jgg@nvidia.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
linux-pci@vger.kernel.org, "Kevin Tian" <kevin.tian@intel.com>,
"Lu Baolu" <baolu.lu@linux.intel.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Tony Zhu" <tony.zhu@intel.com>, "Joerg Roedel" <jroedel@suse.de>
Subject: Re: [PATCH] PCI: revert "Enable PASID only when ACS RR & UF enabled on upstream path"
Date: Wed, 11 Jan 2023 10:36:37 -0400 [thread overview]
Message-ID: <Y77JdR5LgjFnP7FI@nvidia.com> (raw)
In-Reply-To: <41e25f9f-b106-de77-97ab-d50196de7514@amd.com>
On Wed, Jan 11, 2023 at 03:07:36PM +0100, Christian König wrote:
> Well no, we can perfectly fine enable this as we have done in the past.
> What we can't do is rejecting it without driver specific knowledge,
> because the hardware might still work correctly.
It is an interesting point that any device using PASID for SVA must
necessary also be doing ATS/PRI and thus must always be setting the
translated bit in their Mem TLPs
So, at least at this instant in the kernel we have no need for the ACS
check as everything is SVA.
This is forward looking where we are going to have non SVA uses of
PASIDs and we cannot guarantee translated TLPs.
Keep in mind this is pretty much an integrity problem, eg if I allow
iommufd to assign page tables to a PASID without PRI we can get bad
behaviors if the HW does not route properly.
So we are justified to be conservative here to prevent data corruption
in bad cases.
Jason
prev parent reply other threads:[~2023-01-11 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 8:57 [PATCH] PCI: revert "Enable PASID only when ACS RR & UF enabled on upstream path" Christian König
2023-01-11 9:15 ` Christian König
2023-01-11 10:04 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-11 13:07 ` Jason Gunthorpe
2023-01-11 13:38 ` Christian König
2023-01-11 13:44 ` Jason Gunthorpe
2023-01-11 13:54 ` Baolu Lu
2023-01-11 14:14 ` Jason Gunthorpe
2023-01-11 14:17 ` Christian König
2023-01-11 14:20 ` Jason Gunthorpe
2023-01-11 14:24 ` Christian König
2023-01-12 8:59 ` Baolu Lu
[not found] ` <41e25f9f-b106-de77-97ab-d50196de7514@amd.com>
2023-01-11 14:36 ` 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=Y77JdR5LgjFnP7FI@nvidia.com \
--to=jgg@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=jroedel@suse.de \
--cc=kevin.tian@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=tony.zhu@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