From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"Rodel, Jorg" <jroedel@suse.de>
Cc: baolu.lu@linux.intel.com,
"Christian König" <christian.koenig@amd.com>,
"Jason Gunthorpe" <jgg@nvidia.com>,
"Vasant Hegde" <vasant.hegde@amd.com>,
"Zhu, Tony" <tony.zhu@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Matt Fagnani" <matt.fagnani@bell.net>
Subject: Re: [PATCH v2 1/1] PCI: Add translated request only flag for pci_enable_pasid()
Date: Fri, 13 Jan 2023 10:36:37 +0800 [thread overview]
Message-ID: <3b2c162f-7ba2-5e84-2389-a8686c772467@linux.intel.com> (raw)
In-Reply-To: <BN9PR11MB52765287D7C66D9CF52F143E8CC29@BN9PR11MB5276.namprd11.prod.outlook.com>
On 2023/1/13 10:24, Tian, Kevin wrote:
>> From: Lu Baolu <baolu.lu@linux.intel.com>
>> Sent: Friday, January 13, 2023 9:44 AM
>>
>> One alternative is ATS which lets the device resolve the PASID+addr pair
>> before a memory request is made into a routeable TLB address through the
>> TA. Those resolved addresses are then cached on the device instead of
>> in the IOMMU TLB and the device always sets the translated bit for PASID.
>> One example of those devices are AMD graphic devices that always have ACS
>> or ATS enabled together with PASID.
>
> this should be made clear that ATS alone doesn't imply that translated
> bit is always set. It's just an optimization so the device may cache
> translation for selective requests. Only combining with PRI to
> support SVA has such implication.
>
>> + * @flags: device-specific flags
>> + * - PCI_PASID_XLATED_REQ_ONLY: The PCI device only issues PASID
>> + * memory requests of translated type.
>
> this reads like the device even doesn't issue non-PASID requests.
>
> It is clearer to be "The PCI device always use translated type for all
> PASID memory requests".
>
> Otherwise looks good to me:
>
> Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Both make sense to me. It's updated. Thanks a lot!
--
Best regards,
baolu
next prev parent reply other threads:[~2023-01-13 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 1:44 [PATCH v2 1/1] PCI: Add translated request only flag for pci_enable_pasid() Lu Baolu
2023-01-13 2:24 ` Tian, Kevin
2023-01-13 2:36 ` Baolu Lu [this message]
2023-01-13 8:15 ` Matt Fagnani
2023-01-13 8:49 ` Baolu Lu
2023-01-13 8:51 ` Matt Fagnani
2023-01-14 7:45 ` Baolu Lu
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=3b2c162f-7ba2-5e84-2389-a8686c772467@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jroedel@suse.de \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matt.fagnani@bell.net \
--cc=tony.zhu@intel.com \
--cc=vasant.hegde@amd.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