From: Lu Baolu <baolu.lu@linux.intel.com>
To: David Woodhouse <dwmw2@infradead.org>, Joerg Roedel <joro@8bytes.org>
Cc: ashok.raj@intel.com, sanjay.k.kumar@intel.com,
jacob.jun.pan@intel.com, kevin.tian@intel.com,
yi.l.liu@intel.com, yi.y.sun@intel.com,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] iommu/vt-d: Global PASID name space
Date: Mon, 26 Mar 2018 08:38:21 +0800 [thread overview]
Message-ID: <5AB840FD.8020600@linux.intel.com> (raw)
In-Reply-To: <1521081501-30119-1-git-send-email-baolu.lu@linux.intel.com>
Hi Joerg,
A gentle ping. :-)
Any comments on this patch set?
Best regards,
Lu Baolu
On 03/15/2018 10:38 AM, Lu Baolu wrote:
> Hi,
>
> This patch series is trying to change the scope of PASID management
> used in Intel IOMMU driver from per IOMMU to driver global. This is
> required for some cases where current per-IOMMU PASID name space
> doesn't work. For an example, one application (associated with one
> PASID) might talk to two physical devices simultaneously where two
> devices could reside behind two different IOMMU units.
>
> Best regards,
> Lu Baolu
>
> Lu Baolu (3):
> iommu/vt-d: Global PASID name space
> iommu/vt-d: Decouple idr bond pointer from svm
> iommu/vt-d: Use global PASID for SVM usage
>
> drivers/iommu/intel-iommu.c | 64 +++++++++++++++++++++++++++++++++++++++++++++
> drivers/iommu/intel-svm.c | 34 +++++++++++++-----------
> include/linux/intel-iommu.h | 7 ++++-
> 3 files changed, 89 insertions(+), 16 deletions(-)
>
next prev parent reply other threads:[~2018-03-26 0:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 2:38 Lu Baolu
2018-03-15 2:38 ` [PATCH 1/3] " Lu Baolu
2018-03-15 2:38 ` [PATCH 2/3] iommu/vt-d: Decouple idr bond pointer from svm Lu Baolu
2018-03-15 2:38 ` [PATCH 3/3] iommu/vt-d: Use global PASID for SVM usage Lu Baolu
2018-03-26 0:38 ` Lu Baolu [this message]
2018-03-29 8:52 ` [PATCH 0/3] iommu/vt-d: Global PASID name space Joerg Roedel
2018-03-29 23:38 ` Lu Baolu
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=5AB840FD.8020600@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sanjay.k.kumar@intel.com \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@intel.com \
/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
Powered by JetHome