From: Jason Gunthorpe <jgg@nvidia.com>
To: iommu@lists.linux.dev, Joerg Roedel <joro@8bytes.org>,
linux-arm-kernel@lists.infradead.org,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
dri-devel@lists.freedesktop.org,
Liviu Dudau <liviu.dudau@arm.com>,
patches@lists.linux.dev, Steven Price <steven.price@arm.com>
Subject: [PATCH v2 0/3] Remove split on unmap behavior
Date: Mon, 4 Nov 2024 13:41:28 -0400 [thread overview]
Message-ID: <0-v2-fd55d00a60b2+c69-arm_no_split_jgg@nvidia.com> (raw)
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.
v2:
- 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 | 125 +----------------------------
drivers/iommu/io-pgtable-arm.c | 68 +---------------
drivers/iommu/iommu.c | 14 ++++
3 files changed, 20 insertions(+), 187 deletions(-)
base-commit: 8e929cb546ee42c9a61d24fae60605e9e3192354
--
2.43.0
next reply other threads:[~2024-11-04 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 17:41 Jason Gunthorpe [this message]
2024-11-04 17:41 ` [PATCH v2 1/3] iommu/io-pgtable-arm: Remove split on unmap behavior Jason Gunthorpe
2024-11-04 18:38 ` Liviu Dudau
2024-11-06 15:12 ` Steven Price
2024-11-04 17:41 ` [PATCH v2 2/3] iommu/io-pgtable-arm-v7s: " Jason Gunthorpe
2024-11-04 19:53 ` Robin Murphy
2024-11-04 20:09 ` Jason Gunthorpe
2024-11-05 16:59 ` Will Deacon
2024-11-05 17:11 ` Jason Gunthorpe
2024-11-04 17:41 ` [PATCH v2 3/3] iommu: Add a kdoc to iommu_unmap() Jason Gunthorpe
2024-11-04 18:42 ` Liviu Dudau
2024-11-05 3:46 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0-v2-fd55d00a60b2+c69-arm_no_split_jgg@nvidia.com \
--to=jgg@nvidia.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=patches@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=steven.price@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).