From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
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: Thu, 28 May 2020 08:33:20 -0700 [thread overview]
Message-ID: <20200528083320.56aa5e60@jacob-builder> (raw)
In-Reply-To: <00f0597f-b235-b92e-ad41-a7ffcff9b59b@linux.intel.com>
On Thu, 28 May 2020 11:32:50 +0800
Lu Baolu <baolu.lu@linux.intel.com> wrote:
> Hi Jorge,
>
> On 2020/5/27 20:42, Joerg Roedel wrote:
> > Hi Jean-Philippe,
> >
> > On Wed, May 27, 2020 at 12:10:38PM +0200, Jean-Philippe Brucker
> > wrote:
> >> I was wondering if you could take these two patches for v5.8. The
> >> API change is a precursor for the SVA support in SMMUv3, and the
> >> VT-d implementation of the SVA API (queued for 5.8) doesn't
> >> implement iommu_sva_ops.
> >
> > I'd like some Acks on patch 2 (at least from the Intel people)
> > before going ahead with this.
> >
>
> Patch 2 in this series looks good to me.
>
> Acked-by: Lu Baolu <baolu.lu@linux.intel.com>
>
> +Jacob, he participated in the discussions.
>
Patch 2 looks good to me, VT-d has a similar flow and challenge to stop
DMA in mm_exit. We disable fault reporting during this window between
mm_exit and FD close trigged unbind.
Acked-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
> Best regards,
> baolu
[Jacob Pan]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-05-28 15:27 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 [this message]
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=20200528083320.56aa5e60@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=baolu.lu@linux.intel.com \
--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 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).