iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Neo Jia <cjia@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Lu Baolu <baolu.lu@linux.intel.com>,
	Joerg Roedel <joro@8bytes.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Kirti Wankhede <kwankhede@nvidia.com>,
	ashok.raj@intel.com, sanjay.k.kumar@intel.com,
	jacob.jun.pan@intel.com, kevin.tian@intel.com,
	Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
	yi.l.liu@intel.com, yi.y.sun@intel.com, peterx@redhat.com,
	tiwei.bie@intel.com, xin.zeng@intel.com,
	iommu@lists.linux-foundation.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: Re: [PATCH v7 9/9] vfio/type1: Handle different mdev isolation type
Date: Fri, 8 Mar 2019 10:03:18 -0800	[thread overview]
Message-ID: <20190308180317.GA30821@nvidia.com> (raw)
In-Reply-To: <20190307165623.1834cc93@w520.home>

On Thu, Mar 07, 2019 at 04:56:23PM -0700, Alex Williamson wrote:
> On Thu, 7 Mar 2019 00:44:54 -0800
> Neo Jia <cjia@nvidia.com> wrote:
> 
> > On Fri, Feb 22, 2019 at 10:19:27AM +0800, Lu Baolu wrote:
> > > This adds the support to determine the isolation type
> > > of a mediated device group by checking whether it has
> > > an iommu device. If an iommu device exists, an iommu
> > > domain will be allocated and then attached to the iommu
> > > device. Otherwise, keep the same behavior as it is.
> > > 
> > > Cc: Ashok Raj <ashok.raj@intel.com>
> > > Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>
> > > Cc: Kevin Tian <kevin.tian@intel.com>
> > > Signed-off-by: Sanjay Kumar <sanjay.k.kumar@intel.com>
> > > Signed-off-by: Liu Yi L <yi.l.liu@intel.com>
> > > Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> > > Reviewed-by: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
> > > ---
> > >  drivers/vfio/vfio_iommu_type1.c | 48 ++++++++++++++++++++++++++++-----
> > >  1 file changed, 41 insertions(+), 7 deletions(-)
> > > 
> > > diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> > > index ccc4165474aa..f1392c582a3c 100644
> > > --- a/drivers/vfio/vfio_iommu_type1.c
> > > +++ b/drivers/vfio/vfio_iommu_type1.c
> > > @@ -1368,13 +1368,40 @@ static void vfio_iommu_detach_group(struct vfio_domain *domain,
> > >  		iommu_detach_group(domain->domain, group->iommu_group);
> > >  }
> > >    
> > 
> > Hi Baolu,
> > 
> > To allow IOMMU-awared mdev, I think you need to modify the
> > vfio_iommu_type1_pin_pages and vfio_iommu_type1_unpin_pages to remove the
> > iommu->external_domain check.
> > 
> > Could you please include that in your patch? If not, I can send out a separate
> > patch to address that issue.
> 
> I figured it was intentional that an IOMMU backed mdev would not use
> the pin/unpin interface and therefore the exiting -EINVAL returns would
> be correct.  Can you elaborate on the use case for still requiring the
> mdev pin/unpin interface for these devices?  Thanks,

Sure. We are using this api to fetch a pfn of a guest physical address so we can
access it for PV.

Thanks,
Neo

> 
> Alex

  reply	other threads:[~2019-03-08 18:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22  2:19 [PATCH v7 0/9] vfio/mdev: IOMMU aware mediated device Lu Baolu
2019-02-22  2:19 ` [PATCH v7 1/9] iommu: Add APIs for multiple domains per device Lu Baolu
2019-02-22  2:19 ` [PATCH v7 2/9] iommu/vt-d: Move enable pasid out of CONFIG_INTEL_IOMMU_SVM Lu Baolu
2019-02-22  2:19 ` [PATCH v7 3/9] iommu/vt-d: Add per-device IOMMU feature ops entries Lu Baolu
2019-02-22  2:19 ` [PATCH v7 4/9] iommu/vt-d: Move common code out of iommu_attch_device() Lu Baolu
2019-02-22  2:19 ` [PATCH v7 5/9] iommu/vt-d: Aux-domain specific domain attach/detach Lu Baolu
2019-02-22  2:19 ` [PATCH v7 6/9] iommu/vt-d: Return ID associated with an auxiliary domain Lu Baolu
2019-02-22  2:19 ` [PATCH v7 7/9] vfio/mdev: Add iommu related member in mdev_device Lu Baolu
2019-02-22 14:34   ` Christoph Hellwig
2019-02-22 15:31     ` Alex Williamson
2019-02-22  2:19 ` [PATCH v7 8/9] vfio/type1: Add domain at(de)taching group helpers Lu Baolu
2019-03-26  9:33   ` Kirti Wankhede
2019-02-22  2:19 ` [PATCH v7 9/9] vfio/type1: Handle different mdev isolation type Lu Baolu
     [not found]   ` <20190222021927.13132-10-baolu.lu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2019-03-07  8:44     ` Neo Jia
2019-03-07 23:56       ` Alex Williamson
2019-03-08 18:03         ` Neo Jia [this message]
2019-03-20  5:52           ` Lu Baolu
2019-02-26 10:37 ` [PATCH v7 0/9] vfio/mdev: IOMMU aware mediated device 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=20190308180317.GA30821@nvidia.com \
    --to=cjia@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=ashok.raj@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jacob.jun.pan@intel.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=jean-philippe.brucker@arm.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterx@redhat.com \
    --cc=sanjay.k.kumar@intel.com \
    --cc=tiwei.bie@intel.com \
    --cc=xin.zeng@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;
as well as URLs for NNTP newsgroup(s).