linux-kernel - RE: [PATCH v4 3/7] iommu: Support allocation of global PASIDs outside SVA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BN9PR11MB5276D09F18BA65AD074777948C9A9@BN9PR11MB5276.namprd11.prod.outlook.com>
Date:   Tue, 11 Apr 2023 08:02:55 +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>,
        Robin Murphy <robin.murphy@....com>,
        Jason Gunthorpe <jgg@...dia.com>,
        Lu Baolu <baolu.lu@...ux.intel.com>,
        Joerg Roedel <joro@...tes.org>,
        "dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
        "vkoul@...nel.org" <vkoul@...nel.org>
CC:     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>,
        "Jiang, Dave" <dave.jiang@...el.com>,
        "Luck, Tony" <tony.luck@...el.com>,
        "Zanussi, Tom" <tom.zanussi@...el.com>
Subject: RE: [PATCH v4 3/7] iommu: Support allocation of global PASIDs outside
 SVA

> From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
> Sent: Saturday, April 8, 2023 2:06 AM
> @@ -28,8 +26,8 @@ static int iommu_sva_alloc_pasid(struct mm_struct
> *mm, ioasid_t min, ioasid_t ma
>  		goto out;
>  	}
> 
> -	ret = ida_alloc_range(&iommu_global_pasid_ida, min, max,
> GFP_KERNEL);
> -	if (ret < min)
> +	ret = iommu_alloc_global_pasid(min, max);

I wonder whether this can take a device pointer so dev->iommu->max_pasids
is enforced inside the alloc function.

and do we even need the min/max parameters? With special pasids reserved
then what driver needs is just to get a free pasid from the global space within
dev->iommu->max_pasids constraint...

iommu_sva_alloc_pasid() can be reworked to avoid min/max by taking a 
device pointer too.