From: Lu Baolu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
"Pan, Jacob jun" <jacob.jun.pan@intel.com>,
"Raj, Ashok" <ashok.raj@intel.com>,
"Liu, Yi L" <yi.l.liu@intel.com>
Cc: baolu.lu@linux.intel.com,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] iommu/vt-d: Set PGSNP bit in pasid table entry for SVA binding
Date: Fri, 22 Apr 2022 21:13:35 +0800 [thread overview]
Message-ID: <8440e43b-aa1f-2648-6b64-afc34aa97bc2@linux.intel.com> (raw)
In-Reply-To: <BN9PR11MB5276EDDABE40B6A6A67A0F4E8CF79@BN9PR11MB5276.namprd11.prod.outlook.com>
On 2022/4/22 11:05, Tian, Kevin wrote:
>> From: Lu Baolu <baolu.lu@linux.intel.com>
>> Sent: Thursday, April 21, 2022 7:36 PM
>>
>> This field make the requests snoop processor caches irrespective of
>> other attributes in the request or other fields in paging structure
>> entries used to translate the request.
>
> I think you want to first point out the fact that SVA wants snoop
> cache instead of just talking about the effect of PGSNP.
>
> But thinking more I wonder why PGSNP is ever required. This is
> similar to DMA API case. x86 is already cache coherent for normal
> DMA (if not setting PCI no-snoop) and if the driver knows no-snoop
> is incompatible to SVA API then it should avoid triggering no-snoop
> traffic for SVA usage. In this case it is pointless for IOMMU driver
> to enable force-snooping. Even in the future certain platform allows
> no-snoop usage w/ SVA (I'm not sure how it works) this again should
> be reflected by additional SVA APIs for driver to explicitly manage.
>
> force-snoop should be enabled only in device assignment case IMHO,
> orthogonal to whether vSVA is actually used.
>
> Did I misunderstand the motivation here?
No, you didn't.
Let's talk with the arch guys for more details before move this patch
ahead. Thanks for pointing this out.
Best regards,
baolu
>
>>
>> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
>> ---
>> drivers/iommu/intel/svm.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/iommu/intel/svm.c b/drivers/iommu/intel/svm.c
>> index 23a38763c1d1..c720d1be992d 100644
>> --- a/drivers/iommu/intel/svm.c
>> +++ b/drivers/iommu/intel/svm.c
>> @@ -391,9 +391,12 @@ static struct iommu_sva
>> *intel_svm_bind_mm(struct intel_iommu *iommu,
>> }
>>
>> /* Setup the pasid table: */
>> - sflags = (flags & SVM_FLAG_SUPERVISOR_MODE) ?
>> - PASID_FLAG_SUPERVISOR_MODE : 0;
>> - sflags |= cpu_feature_enabled(X86_FEATURE_LA57) ?
>> PASID_FLAG_FL5LP : 0;
>> + sflags = PASID_FLAG_PAGE_SNOOP;
>> + if (flags & SVM_FLAG_SUPERVISOR_MODE)
>> + sflags |= PASID_FLAG_SUPERVISOR_MODE;
>> + if (cpu_feature_enabled(X86_FEATURE_LA57))
>> + sflags |= PASID_FLAG_FL5LP;
>> +
>> spin_lock_irqsave(&iommu->lock, iflags);
>> ret = intel_pasid_setup_first_level(iommu, dev, mm->pgd, mm-
>>> pasid,
>> FLPT_DEFAULT_DID, sflags);
>> --
>> 2.25.1
>
next prev parent reply other threads:[~2022-04-22 13:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 11:35 [PATCH v2 0/4] iommu/vt-d: Some fine tuning of SVA Lu Baolu
2022-04-21 11:35 ` [PATCH v2 1/4] iommu/vt-d: Check before setting PGSNP bit in pasid table entry Lu Baolu
2022-04-22 2:47 ` Tian, Kevin
2022-04-22 13:04 ` Lu Baolu
2022-04-24 3:37 ` Tian, Kevin
2022-04-24 4:37 ` Lu Baolu
2022-04-24 5:55 ` Tian, Kevin
2022-04-24 6:23 ` Lu Baolu
2022-04-21 11:35 ` [PATCH v2 2/4] iommu/vt-d: Set PGSNP bit in pasid table entry for SVA binding Lu Baolu
2022-04-22 3:05 ` Tian, Kevin
2022-04-22 13:13 ` Lu Baolu [this message]
2022-04-21 11:35 ` [PATCH v2 3/4] iommu/vt-d: Drop stop marker messages Lu Baolu
2022-04-22 3:05 ` Tian, Kevin
2022-04-23 7:32 ` Lu Baolu
2022-04-21 11:35 ` [PATCH v2 4/4] iommu/vt-d: Size Page Request Queue to avoid overflow condition Lu Baolu
2022-04-22 3:07 ` 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=8440e43b-aa1f-2648-6b64-afc34aa97bc2@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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