From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
Joerg Roedel <joro@8bytes.org>, Jason Gunthorpe <jgg@nvidia.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: "Pan, Jacob jun" <jacob.jun.pan@intel.com>,
"Liu, Yi L" <yi.l.liu@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: Check domain force_snooping against attached devices
Date: Thu, 5 May 2022 20:12:24 +0800 [thread overview]
Message-ID: <22359719-15c8-5215-fdf3-7eec60f2c106@linux.intel.com> (raw)
In-Reply-To: <BN9PR11MB5276F768185B4CB64C2D027E8CC29@BN9PR11MB5276.namprd11.prod.outlook.com>
On 2022/5/5 16:43, Tian, Kevin wrote:
>> From: Lu Baolu <baolu.lu@linux.intel.com>
>> Sent: Thursday, May 5, 2022 9:07 AM
>>
>> As domain->force_snooping only impacts the devices attached with the
>> domain, there's no need to check against all IOMMU units. At the same
>> time, for a brand new domain (hasn't been attached to any device), the
>> force_snooping field could be set, but the attach_dev callback will
>> return failure if it wants to attach to a device which IOMMU has no
>> snoop control capability.
>
> The description about brand new domain is not very clear. I think the
> point here is that force_snooping could be set on a domain no matter
> whether it has been attached or not and once set it is an immutable
> flag. If no device attached the operation always succeeds then this
> empty domain can be only attached to a device of which the IOMMU
> supports snoop control.
Exactly. Will update this description.
>
>> static bool intel_iommu_enforce_cache_coherency(struct iommu_domain
>> *domain)
>> {
>> struct dmar_domain *dmar_domain = to_dmar_domain(domain);
>>
>> - if (!domain_update_iommu_snooping(NULL))
>> + if (dmar_domain->force_snooping)
>> + return true;
>> +
>> + if (!domain_support_force_snooping(dmar_domain))
>> return false;
>> +
>
> Who guarantees that domain->devices won't change between
> above condition check and following set operation?
Good catch. Should lift the lock up here.
>
>> + domain_set_force_snooping(dmar_domain);
>> dmar_domain->force_snooping = true;
>> +
>> return true;
>> }
>>
>
> Thanks
> Kevin
Best regards,
baolu
next prev parent reply other threads:[~2022-05-05 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 1:07 [PATCH v2 0/4] iommu/vt-d: Force snooping improvement Lu Baolu
2022-05-05 1:07 ` [PATCH v2 1/4] iommu/vt-d: Block force-snoop domain attaching if no SC support Lu Baolu
2022-05-05 8:34 ` Tian, Kevin
2022-05-05 1:07 ` [PATCH v2 2/4] iommu/vt-d: Check domain force_snooping against attached devices Lu Baolu
2022-05-05 8:43 ` Tian, Kevin
2022-05-05 12:12 ` Baolu Lu [this message]
2022-05-05 1:07 ` [PATCH v2 3/4] iommu/vt-d: Remove domain_update_iommu_snooping() Lu Baolu
2022-05-05 8:44 ` Tian, Kevin
2022-05-05 1:07 ` [PATCH v2 4/4] iommu/vt-d: Remove hard coding PGSNP bit in PASID entries Lu Baolu
2022-05-05 8:46 ` Tian, Kevin
2022-05-05 12:14 ` 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=22359719-15c8-5215-fdf3-7eec60f2c106@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--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