[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50a05134-349a-0921-2a70-63f303bf86a4@linux.intel.com>
Date: Fri, 1 Jul 2022 16:12:23 +0800
From: Baolu Lu <baolu.lu@...ux.intel.com>
To: "Tian, Kevin" <kevin.tian@...el.com>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>
Cc: baolu.lu@...ux.intel.com, "Raj, Ashok" <ashok.raj@...el.com>,
"Liu, Yi L" <yi.l.liu@...el.com>,
"Pan, Jacob jun" <jacob.jun.pan@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 00/11] iommu/vt-d: Optimize the use of locks
On 2022/7/1 15:53, Tian, Kevin wrote:
>> From: Lu Baolu <baolu.lu@...ux.intel.com>
>> Sent: Wednesday, June 29, 2022 3:47 PM
>>
>> v3:
>> - Split reduction of lock ranges from changing irqsave.
>> https://lore.kernel.org/linux-
>> iommu/BN9PR11MB52760A3D7C6BF1AF9C9D34658CAA9@...PR11MB5276.
>> namprd11.prod.outlook.com/
>> - Fully initialize the dev_info before adding it to the list.
>> https://lore.kernel.org/linux-
>> iommu/BN9PR11MB52764D7CD86448C5E4EB46668CAA9@...PR11MB5276.
>> namprd11.prod.outlook.com/
>> - Various code and comments refinement.
>>
>
> This doesn't say why original patch2 was removed:
>
> "iommu/vt-d: Remove for_each_device_domain()"
>
> It took me a while to realize that it's already covered by your another
> patch fixing RID2PASID. 😊
My fault! I forgot to mention it in the change log. Sorry about it.
Best regards,
baolu
Powered by blists - more mailing lists