[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN9PR11MB527645CF20DA53BF9009A9118CBD9@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Fri, 1 Jul 2022 07:53:53 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Lu Baolu <baolu.lu@...ux.intel.com>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>
CC: "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
> 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. 😊
Powered by blists - more mailing lists