[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d658fd8d-00a2-273f-2685-dee55b96705e@linux.intel.com>
Date: Tue, 8 Feb 2022 12:29:57 +0800
From: Lu Baolu <baolu.lu@...ux.intel.com>
To: John Garry <john.garry@...wei.com>, Joerg Roedel <joro@...tes.org>,
Kevin Tian <kevin.tian@...el.com>,
Ashok Raj <ashok.raj@...el.com>, Liu Yi L <yi.l.liu@...el.com>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>
Cc: baolu.lu@...ux.intel.com, linux-kernel@...r.kernel.org,
iommu@...ts.linux-foundation.org, Jason Gunthorpe <jgg@...dia.com>,
Robin Murphy <robin.murphy@....com>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v1 04/10] iommu/vt-d: Remove iova_cache_get/put()
On 2/7/22 6:39 PM, John Garry wrote:
> On 07/02/2022 06:41, Lu Baolu wrote:
>> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
>> index 583ec0fa4ac1..e8d58654361c 100644
>> --- a/drivers/iommu/intel/iommu.c
>> +++ b/drivers/iommu/intel/iommu.c
>> @@ -3348,9 +3348,6 @@ static inline int iommu_devinfo_cache_init(void)
>> static int __init iommu_init_mempool(void)
>> {
>> int ret;
>> - ret = iova_cache_get();
>> - if (ret)
>> - return ret;
>> ret = iommu_domain_cache_init();
>> if (ret)
>> @@ -3362,7 +3359,6 @@ static int __init iommu_init_mempool(void)
>> kmem_cache_destroy(iommu_domain_cache);
>> domain_error:
>
> nit: is this label still really required? only failures in
> iommu_domain_cache_init() jump to it, and that can return directly now.
It will be cleaned up in the next patch.
>
> Thanks,
> John
>
>> - iova_cache_put();
>
Best regards,
baolu
Powered by blists - more mailing lists