From: Joerg Roedel <joro@8bytes.org>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: arnd@arndb.de, gregkh@linuxfoundation.org, jgg@ziepe.ca,
iommu@lists.linux-foundation.org, zhangfei.gao@linaro.org,
linux-accelerators@lists.ozlabs.org
Subject: Re: [PATCH v2 0/2] iommu: Remove iommu_sva_ops::mm_exit()
Date: Fri, 29 May 2020 14:53:11 +0200 [thread overview]
Message-ID: <20200529125310.GA14598@8bytes.org> (raw)
In-Reply-To: <20200423125329.782066-1-jean-philippe@linaro.org>
On Thu, Apr 23, 2020 at 02:53:27PM +0200, Jean-Philippe Brucker wrote:
> 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()
Applied, thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2020-05-29 12:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 12:53 [PATCH v2 0/2] iommu: Remove iommu_sva_ops::mm_exit() Jean-Philippe Brucker
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 [this message]
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=20200529125310.GA14598@8bytes.org \
--to=joro@8bytes.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.