[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN9PR11MB5276EC1F0926256D0E8F05F58CAA9@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Wed, 22 Feb 2023 02:22:48 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Jacob Pan <jacob.jun.pan@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
Jason Gunthorpe <jgg@...dia.com>,
Lu Baolu <baolu.lu@...ux.intel.com>,
Joerg Roedel <joro@...tes.org>,
"Jean-Philippe Brucker" <jean-philippe@...aro.com>
CC: Robin Murphy <robin.murphy@....com>, Will Deacon <will@...nel.org>,
"David Woodhouse" <dwmw2@...radead.org>,
"Raj, Ashok" <ashok.raj@...el.com>,
"Liu, Yi L" <yi.l.liu@...el.com>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
"Hansen, Dave" <dave.hansen@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
"X86 Kernel" <x86@...nel.org>, "Jiang, Dave" <dave.jiang@...el.com>
Subject: RE: [PATCH v3 3/5] iommu/sva: Stop using ioasid_set for SVA
> From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
> Sent: Friday, February 17, 2023 8:00 AM
>
> + ret = ida_alloc_range(&iommu_global_pasid_ida, min, max,
> GFP_KERNEL);
> + if (ret < min)
> + goto out;
ioasid_alloc() currently uses GFP_ATOMIC.
since this is kind of a replacement w/o functional impact, it'd be cleaner
from bisect p.o.v. to have a separate patch changing GFP_ATOMIC
to GFP_KERNEL in ioasid_alloc() and then this patch.
Powered by blists - more mailing lists