diff options
| author | Joerg Roedel <jroedel@suse.de> | 2022-11-03 15:51:48 +0100 |
|---|---|---|
| committer | Joerg Roedel <jroedel@suse.de> | 2022-11-03 15:51:48 +0100 |
| commit | 69e61edebea030f177de7a23b8d5d9b8c4a90bda (patch) | |
| tree | 9c7b6f8bdc58ae3850b5cfbe50797e2e0968efb2 /include/linux/iommu.h | |
| parent | 757636ed2607a3269cd2764e3e4a0480384c6c26 (diff) | |
| parent | 04cee82e04d2aff3d177ef0021ecdff228daf7b8 (diff) | |
| download | lwn-69e61edebea030f177de7a23b8d5d9b8c4a90bda.tar.gz lwn-69e61edebea030f177de7a23b8d5d9b8c4a90bda.zip | |
Merge tag 'for-joerg' of git://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd into core
iommu: Define EINVAL as device/domain incompatibility
This series is to replace the previous EMEDIUMTYPE patch in a VFIO series:
https://lore.kernel.org/kvm/Yxnt9uQTmbqul5lf@8bytes.org/
The purpose is to regulate all existing ->attach_dev callback functions to
use EINVAL exclusively for an incompatibility error between a device and a
domain. This allows VFIO and IOMMUFD to detect such a soft error, and then
try a different domain with the same device.
Among all the patches, the first two are preparatory changes. And then one
patch to update kdocs and another three patches for the enforcement
effort.
Link: https://lore.kernel.org/r/cover.1666042872.git.nicolinc@nvidia.com
Diffstat (limited to 'include/linux/iommu.h')
| -rw-r--r-- | include/linux/iommu.h | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/include/linux/iommu.h b/include/linux/iommu.h index 7d2648058e43..68d7d304cdb7 100644 --- a/include/linux/iommu.h +++ b/include/linux/iommu.h @@ -278,6 +278,18 @@ struct iommu_ops { /** * struct iommu_domain_ops - domain specific operations * @attach_dev: attach an iommu domain to a device + * Return: + * * 0 - success + * * EINVAL - can indicate that device and domain are incompatible due to + * some previous configuration of the domain, in which case the + * driver shouldn't log an error, since it is legitimate for a + * caller to test reuse of existing domains. Otherwise, it may + * still represent some other fundamental problem + * * ENOMEM - out of memory + * * ENOSPC - non-ENOMEM type of resource allocation failures + * * EBUSY - device is attached to a domain and cannot be changed + * * ENODEV - device specific errors, not able to be attached + * * <others> - treated as ENODEV by the caller. Use is discouraged * @detach_dev: detach an iommu domain from a device * @set_dev_pasid: set an iommu domain to a pasid of device * @map: map a physically contiguous memory region to an iommu domain |