From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Zhangfei Gao <zhangfei.gao@linaro.org>
Cc: gregkh@linuxfoundation.org, iommu@lists.linux-foundation.org,
arnd@arndb.de, linux-accelerators@lists.ozlabs.org, jgg@ziepe.ca
Subject: Re: [PATCH 1/2] uacce: Remove mm_exit() op
Date: Thu, 9 Apr 2020 11:44:50 +0200 [thread overview]
Message-ID: <20200409094450.GI2435@myrica> (raw)
In-Reply-To: <5741a4d9-c3ae-f0d6-27f9-550bbeaa4c4a@linaro.org>
On Thu, Apr 09, 2020 at 05:07:34PM +0800, Zhangfei Gao wrote:
>
>
> On 2020/4/8 下午10:04, Jean-Philippe Brucker wrote:
> > The mm_exit() op will be removed from the SVA API. When a process dies
> > and its mm goes away, the IOMMU driver won't notify device drivers
> > anymore. Drivers should expect to handle a lot more aborted DMA. On the
> > upside, it does greatly simplify the queue management.
> >
> > The uacce_mm struct, that tracks all queues bound to an mm, was only
> > used by the mm_exit() callback. Remove it.
> >
> > Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> Thanks Jean for doing this.
>
> Tested-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>
> Except one line.
> > -static void uacce_mm_put(struct uacce_queue *q)
> > +static void uacce_unbind_queue(struct uacce_queue *q)
> > {
> > - struct uacce_mm *uacce_mm = q->uacce_mm;
> > -
> > - lockdep_assert_held(&q->uacce->mm_lock);
> > -
> > - mutex_lock(&uacce_mm->lock);
> > - list_del(&q->list);
> > - mutex_unlock(&uacce_mm->lock);
> > -
> > - if (list_empty(&uacce_mm->queues)) {
> > - if (uacce_mm->handle)
> > - iommu_sva_unbind_device(uacce_mm->handle);
> > - list_del(&uacce_mm->list);
> > - kfree(uacce_mm);
> > - }
> > + if (!q->handle)
> > + return;
> > + iommu_sva_unbind_device(q->handle);
> + q->handle = 0;
>
> Otherwise iommu_sva_unbind_device maybe called twice.
> Since uacce_unbind_queue can be called by uacce_remove and uacce_fops_release.
Thanks, I'll add it in v2
Jean
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-04-09 9:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 14:04 [PATCH 0/2] iommu: Remove iommu_sva_ops::mm_exit() Jean-Philippe Brucker
2020-04-08 14:04 ` [PATCH 1/2] uacce: Remove mm_exit() op Jean-Philippe Brucker
2020-04-09 9:07 ` Zhangfei Gao
2020-04-09 9:44 ` Jean-Philippe Brucker [this message]
2020-04-08 14:04 ` [PATCH 2/2] iommu: Remove iommu_sva_ops::mm_exit() Jean-Philippe Brucker
2020-04-08 18:35 ` [PATCH 0/2] " Jacob Pan
2020-04-08 19:02 ` Jason Gunthorpe
2020-04-08 21:35 ` Jacob Pan
2020-04-08 22:32 ` Jason Gunthorpe
2020-04-08 23:48 ` Jacob Pan
2020-04-09 6:39 ` Jean-Philippe Brucker
2020-04-09 14:14 ` Jacob Pan
2020-04-09 14:25 ` Jason Gunthorpe
2020-04-09 16:21 ` Jacob Pan
2020-04-09 16:58 ` Jason Gunthorpe
2020-04-09 14:50 ` Jean-Philippe Brucker
2020-04-09 16:27 ` Jacob Pan
2020-04-10 15:52 ` Jacob Pan
2020-04-15 7:47 ` Jean-Philippe Brucker
2020-04-16 20:58 ` Jacob Pan
2020-04-20 8:02 ` Jean-Philippe Brucker
2020-04-09 12:08 ` Jason Gunthorpe
2020-04-09 16:31 ` Jacob Pan
2020-04-08 23:49 ` Fenghua Yu
2020-04-09 12:12 ` Jason Gunthorpe
2020-04-08 19:04 ` Jason Gunthorpe
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=20200409094450.GI2435@myrica \
--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