[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230801063125.34995-1-baolu.lu@linux.intel.com>
Date: Tue, 1 Aug 2023 14:31:23 +0800
From: Lu Baolu <baolu.lu@...ux.intel.com>
To: Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Jason Gunthorpe <jgg@...pe.ca>,
Kevin Tian <kevin.tian@...el.com>,
Jean-Philippe Brucker <jean-philippe@...aro.org>,
Nicolin Chen <nicolinc@...dia.com>
Cc: Yi Liu <yi.l.liu@...el.com>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>,
iommu@...ts.linux.dev, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Lu Baolu <baolu.lu@...ux.intel.com>
Subject: [PATCH 0/2] iommu: Make pasid array per device
The PCI PASID enabling interface guarantees that the address space used
by each PASID is unique. This is achieved by checking that the PCI ACS
path is enabled for the device. If the path is not enabled, then the
PASID feature cannot be used.
if (!pci_acs_path_enabled(pdev, NULL, PCI_ACS_RR | PCI_ACS_UF))
return -EINVAL;
The PASID array is not an attribute of the IOMMU group. It is more
natural to store the PASID array in the per-device IOMMU data. This
makes the code clearer and easier to understand. No functional changes
are intended.
Please help review and suggest.
Lu Baolu (2):
iommu: Consolidate pasid dma ownership check
iommu: Move pasid array from group to device
include/linux/iommu.h | 2 +
drivers/iommu/iommu.c | 105 +++++++++++++++++-------------------------
2 files changed, 43 insertions(+), 64 deletions(-)
--
2.34.1
Powered by blists - more mailing lists