From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
Joerg Roedel <joro@8bytes.org>,
"Raj, Ashok" <ashok.raj@intel.com>,
Christoph Hellwig <hch@infradead.org>,
Jason Gunthorpe <jgg@nvidia.com>
Cc: baolu.lu@linux.intel.com, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"Liu, Yi L" <yi.l.liu@intel.com>,
"Pan, Jacob jun" <jacob.jun.pan@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 11/12] iommu/vt-d: Use device_domain_lock accurately
Date: Tue, 14 Jun 2022 15:47:21 +0800 [thread overview]
Message-ID: <76dfe89b-67a1-bbea-0c63-18790adb7b9d@linux.intel.com> (raw)
In-Reply-To: <BN9PR11MB52764D7CD86448C5E4EB46668CAA9@BN9PR11MB5276.namprd11.prod.outlook.com>
On 2022/6/14 15:16, Tian, Kevin wrote:
>> From: Lu Baolu <baolu.lu@linux.intel.com>
>> Sent: Tuesday, June 14, 2022 10:52 AM
>>
>> The device_domain_lock is used to protect the device tracking list of
>> a domain. Remove unnecessary spin_lock/unlock()'s and move the necessary
>> ones around the list access.
>>
>> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
>> ---
>> drivers/iommu/intel/iommu.c | 68 +++++++++++++++----------------------
>> 1 file changed, 27 insertions(+), 41 deletions(-)
>>
> [...]
>> +iommu_support_dev_iotlb(struct dmar_domain *domain, struct
>> intel_iommu *iommu,
>> + u8 bus, u8 devfn)
>> {
>> - struct device_domain_info *info;
>> -
>> - assert_spin_locked(&device_domain_lock);
>> + struct device_domain_info *info = NULL, *tmp;
>> + unsigned long flags;
>>
>> if (!iommu->qi)
>> return NULL;
>>
>> - list_for_each_entry(info, &domain->devices, link)
>> - if (info->iommu == iommu && info->bus == bus &&
>> - info->devfn == devfn) {
>> - if (info->ats_supported && info->dev)
>> - return info;
>> + spin_lock_irqsave(&device_domain_lock, flags);
>> + list_for_each_entry(tmp, &domain->devices, link) {
>> + if (tmp->iommu == iommu && tmp->bus == bus &&
>> + tmp->devfn == devfn) {
>> + if (tmp->ats_supported)
>> + info = tmp;
>
> Directly returning with unlock here is clearer than adding
> another tmp variable...
Sure.
>
>> @@ -2460,15 +2450,14 @@ static int domain_add_dev_info(struct
>> dmar_domain *domain, struct device *dev)
>> if (!iommu)
>> return -ENODEV;
>>
>> - spin_lock_irqsave(&device_domain_lock, flags);
>> - info->domain = domain;
>> ret = domain_attach_iommu(domain, iommu);
>> - if (ret) {
>> - spin_unlock_irqrestore(&device_domain_lock, flags);
>> + if (ret)
>> return ret;
>> - }
>> +
>> + spin_lock_irqsave(&device_domain_lock, flags);
>> list_add(&info->link, &domain->devices);
>> spin_unlock_irqrestore(&device_domain_lock, flags);
>> + info->domain = domain;
>>
>
> This is incorrect. You need fully initialize the object before adding
> it to the list. Otherwise a search right after above unlock and
> before assigning info->domain will get a wrong data
Fair enough. Will fix it in the next version.
Best regards,
baolu
next prev parent reply other threads:[~2022-06-14 7:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 2:51 [PATCH v2 00/12] iommu/vt-d: Optimize the use of locks Lu Baolu
2022-06-14 2:51 ` [PATCH v2 01/12] iommu/vt-d: debugfs: Remove device_domain_lock usage Lu Baolu
2022-06-14 6:43 ` Tian, Kevin
2022-06-14 7:15 ` Baolu Lu
2022-06-15 1:53 ` Baolu Lu
2022-06-15 6:13 ` Tian, Kevin
2022-06-15 13:02 ` Baolu Lu
2022-06-14 2:51 ` [PATCH v2 02/12] iommu/vt-d: Remove for_each_device_domain() Lu Baolu
2022-06-14 2:51 ` [PATCH v2 03/12] iommu/vt-d: Remove clearing translation data in disable_dmar_iommu() Lu Baolu
2022-06-14 6:49 ` Tian, Kevin
2022-06-14 7:21 ` Baolu Lu
2022-06-15 6:22 ` Tian, Kevin
2022-06-15 13:10 ` Baolu Lu
2022-06-16 4:00 ` Tian, Kevin
2022-06-14 2:51 ` [PATCH v2 04/12] iommu/vt-d: Use pci_get_domain_bus_and_slot() in pgtable_walk() Lu Baolu
2022-06-14 2:51 ` [PATCH v2 05/12] iommu/vt-d: Unnecessary spinlock for root table alloc and free Lu Baolu
2022-06-14 2:51 ` [PATCH v2 06/12] iommu/vt-d: Acquiring lock in domain ID allocation helpers Lu Baolu
2022-06-14 6:52 ` Tian, Kevin
2022-06-14 7:22 ` Baolu Lu
2022-06-14 2:51 ` [PATCH v2 07/12] iommu/vt-d: Acquiring lock in pasid manipulation helpers Lu Baolu
2022-06-14 2:51 ` [PATCH v2 08/12] iommu/vt-d: Replace spin_lock_irqsave() with spin_lock() Lu Baolu
2022-06-14 6:56 ` Tian, Kevin
2022-06-14 2:51 ` [PATCH v2 09/12] iommu/vt-d: Check device list of domain in domain free path Lu Baolu
2022-06-14 6:57 ` Tian, Kevin
2022-06-14 2:51 ` [PATCH v2 10/12] iommu/vt-d: Fold __dmar_remove_one_dev_info() into its caller Lu Baolu
2022-06-14 7:07 ` Tian, Kevin
2022-06-14 7:44 ` Baolu Lu
2022-06-14 2:51 ` [PATCH v2 11/12] iommu/vt-d: Use device_domain_lock accurately Lu Baolu
2022-06-14 7:16 ` Tian, Kevin
2022-06-14 7:47 ` Baolu Lu [this message]
2022-06-14 2:51 ` [PATCH v2 12/12] iommu/vt-d: Convert global spinlock into per domain ones Lu Baolu
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=76dfe89b-67a1-bbea-0c63-18790adb7b9d@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=hch@infradead.org \
--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=robin.murphy@arm.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).