From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: iommu@lists.linux-foundation.org, linux-accelerators@lists.ozlabs.org
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
arnd@arndb.de, gregkh@linuxfoundation.org, jgg@ziepe.ca,
zhangfei.gao@linaro.org
Subject: [PATCH v2 0/2] iommu: Remove iommu_sva_ops::mm_exit()
Date: Thu, 23 Apr 2020 14:53:27 +0200 [thread overview]
Message-ID: <20200423125329.782066-1-jean-philippe@linaro.org> (raw)
The IOMMU SVA API currently requires device drivers to implement an
mm_exit() callback, which stops device jobs that do DMA. This function
is called in the release() MMU notifier, when an address space that is
shared with a device exits.
It has been noted several time during discussions about SVA that
cancelling DMA jobs can be slow and complex, and doing it in the
release() notifier might cause synchronization issues. Device drivers
must in any case call unbind() to remove their bond, after stopping DMA
from a more favorable context (release of a file descriptor).
Patch 1 removes the mm_exit() callback from the uacce module, and patch
2 removes it from the IOMMU API. Since v1 [1] I fixed the uacce unbind
reported by Zhangfei and added details in the commit message of patch 2.
Jean-Philippe Brucker (2):
uacce: Remove mm_exit() op
iommu: Remove iommu_sva_ops::mm_exit()
include/linux/iommu.h | 30 -------
include/linux/uacce.h | 34 ++------
drivers/iommu/iommu.c | 11 ---
drivers/misc/uacce/uacce.c | 172 +++++++++----------------------------
4 files changed, 51 insertions(+), 196 deletions(-)
--
2.26.0
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2020-04-23 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 12:53 Jean-Philippe Brucker [this message]
2020-04-23 12:53 ` [PATCH v2 1/2] uacce: Remove mm_exit() op Jean-Philippe Brucker
2020-04-24 1:05 ` Zhangfei Gao
2020-04-23 12:53 ` [PATCH v2 2/2] iommu: Remove iommu_sva_ops::mm_exit() Jean-Philippe Brucker
2020-05-27 10:10 ` [PATCH v2 0/2] " Jean-Philippe Brucker
2020-05-27 12:42 ` Joerg Roedel
2020-05-28 3:32 ` Lu Baolu
2020-05-28 3:34 ` Lu Baolu
2020-05-28 15:33 ` Jacob Pan
2020-05-29 12:53 ` Joerg Roedel
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=20200423125329.782066-1-jean-philippe@linaro.org \
--to=jean-philippe@linaro.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jgg@ziepe.ca \
--cc=linux-accelerators@lists.ozlabs.org \
--cc=zhangfei.gao@linaro.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).