mbox series

[v3,0/3] Remove split on unmap behavior

Message ID 0-v3-b3a5b5937f56+7bb-arm_no_split_jgg@nvidia.com (mailing list archive)
Headers show
Series Remove split on unmap behavior | expand

Message

Jason Gunthorpe Nov. 5, 2024, 6:14 p.m. UTC 
This is the result of the discussion on removing split. We agreed that
split is not required, and no application should ask for anything that
would not unmap a full large IOPTE.

Instead of split the two ARM drivers will now WARN_ON and return 0. This
is in contrast to what several other drivers do of removing the whole
IOPTE and returning 0.

The kdoc is updated to describe this.

v3:
 - Remove selftest code too
 - Fix copy/paste error in iommu_unmap kdoc
v2: https://patch.msgid.link/r/0-v2-fd55d00a60b2+c69-arm_no_split_jgg@nvidia.com
 - Use WARN_ON instead of duplicating AMD behavior
 - Add arm-v7s patch
 - Write a kdoc for iommu_unmap()
v1: https://patch.msgid.link/r/0-v1-8c5f369ec2e5+75-arm_no_split_jgg@nvidia.com

Jason Gunthorpe (3):
  iommu/io-pgtable-arm: Remove split on unmap behavior
  iommu/io-pgtable-arm-v7s: Remove split on unmap behavior
  iommu: Add a kdoc to iommu_unmap()

 drivers/iommu/io-pgtable-arm-v7s.c | 146 +----------------------------
 drivers/iommu/io-pgtable-arm.c     |  81 +---------------
 drivers/iommu/iommu.c              |  14 +++
 3 files changed, 21 insertions(+), 220 deletions(-)


base-commit: 8e929cb546ee42c9a61d24fae60605e9e3192354