[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230213074941.919324-1-baolu.lu@linux.intel.com>
Date: Mon, 13 Feb 2023 15:49:37 +0800
From: Lu Baolu <baolu.lu@...ux.intel.com>
To: iommu@...ts.linux.dev
Cc: Joerg Roedel <joro@...tes.org>, Jason Gunthorpe <jgg@...dia.com>,
Christoph Hellwig <hch@...radead.org>,
Kevin Tian <kevin.tian@...el.com>,
Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
linux-kernel@...r.kernel.org, Lu Baolu <baolu.lu@...ux.intel.com>
Subject: [PATCH 0/4] iommu: Extend changing default domain to normal group
The IOMMU group sysfs interface allows users to change the default
domain of a group. The current implementation uses device_lock() to make
sure that the devices in the group are not bound to any driver and won't
be bound during the process of changing the default domain. In order to
avoid a possible deadlock caused by lock order of device_lock and
group->mutex, it limits the functionality to singleton groups only.
The recently implemented DMA ownership framework can be applied here to
replace device_lock(). In addition, add an rw lock to ensure that the
iommu ops of the devices is always valid during the process of changing
default domain.
With above replacement and enhancement, the device_lock() could be
removed and the singleton-group-only limitation could be removed.
The whole series is also available on github:
https://github.com/LuBaolu/intel-iommu/commits/iommu-sysfs-default-domain-extension-v1
Please help to review and suggest.
Lu Baolu (4):
iommu: Add dev_iommu->ops_rwsem
iommu: Use group ownership to avoid driver attachment
iommu: Remove unnecessary device_lock()
iommu: Cleanup iommu_change_dev_def_domain()
include/linux/iommu.h | 3 +
drivers/iommu/iommu.c | 187 +++++++++++++++++-------------------------
2 files changed, 78 insertions(+), 112 deletions(-)
--
2.34.1
Powered by blists - more mailing lists