All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: iommu@lists.linux-foundation.org,
	LKML <linux-kernel@vger.kernel.org>,
	Joerg Roedel <joro@8bytes.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
	Rafael Wysocki <rafael.j.wysocki@intel.com>,
	"Liu, Yi L" <yi.l.liu@intel.com>,
	"Tian, Kevin" <kevin.tian@intel.com>,
	Raj Ashok <ashok.raj@intel.com>,
	Jean Delvare <khali@linux-fr.org>,
	"Christoph Hellwig" <hch@infradead.org>,
	"Lu Baolu" <baolu.lu@linux.intel.com>,
	Yi L <yi.l.liu@linux.intel.com>,
	jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH v4 09/22] iommu/vt-d: add svm/sva invalidate function
Date: Fri, 20 Apr 2018 15:36:59 -0700	[thread overview]
Message-ID: <20180420153659.3052139d@jacob-builder> (raw)
In-Reply-To: <20180417131045.7635a63d@w520.home>

On Tue, 17 Apr 2018 13:10:45 -0600
Alex Williamson <alex.williamson@redhat.com> wrote:

> On Mon, 16 Apr 2018 14:48:58 -0700
> Jacob Pan <jacob.jun.pan@linux.intel.com> wrote:
> 
> > When Shared Virtual Address (SVA) is enabled for a guest OS via
> > vIOMMU, we need to provide invalidation support at IOMMU API and
> > driver level. This patch adds Intel VT-d specific function to
> > implement iommu passdown invalidate API for shared virtual address.
> > 
> > The use case is for supporting caching structure invalidation
> > of assigned SVM capable devices. Emulated IOMMU exposes queue
> > invalidation capability and passes down all descriptors from the
> > guest to the physical IOMMU.
> > 
> > The assumption is that guest to host device ID mapping should be
> > resolved prior to calling IOMMU driver. Based on the device handle,
> > host IOMMU driver can replace certain fields before submit to the
> > invalidation queue.
> > 
> > Signed-off-by: Liu, Yi L <yi.l.liu@linux.intel.com>
> > Signed-off-by: Ashok Raj <ashok.raj@intel.com>
> > Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
> > ---
> >  drivers/iommu/intel-iommu.c | 170
> > ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 170
> > insertions(+)
> > 
> > diff --git a/drivers/iommu/intel-iommu.c
> > b/drivers/iommu/intel-iommu.c index cae4042..c765448 100644
> > --- a/drivers/iommu/intel-iommu.c
> > +++ b/drivers/iommu/intel-iommu.c
> > @@ -4973,6 +4973,175 @@ static void
> > intel_iommu_detach_device(struct iommu_domain *domain,
> > dmar_remove_one_dev_info(to_dmar_domain(domain), dev); }
> >  
> > +/*
> > + * 3D array for converting IOMMU generic type-granularity to VT-d
> > granularity
> > + * X indexed by enum iommu_inv_type
> > + * Y indicates request without and with PASID
> > + * Z indexed by enum iommu_inv_granularity
> > + *
> > + * For an example, if we want to find the VT-d granularity
> > encoding for IOTLB
> > + * type, DMA request with PASID, and page selective. The look up
> > indices are:
> > + * [1][1][8], where
> > + * 1: IOMMU_INV_TYPE_TLB
> > + * 1: with PASID
> > + * 8: IOMMU_INV_GRANU_PAGE_PASID
> > + *
> > + * Granu_map array indicates validity of the table. 1: valid, 0:
> > invalid
> > + *
> > + */
> > +const static int
> > inv_type_granu_map[IOMMU_INV_NR_TYPE][2][IOMMU_INV_NR_GRANU] = {
> > +	/* extended dev IOTLBs, for dev-IOTLB, only global is
> > valid,
> > +	   for dev-EXIOTLB, two valid granu */
> > +	{
> > +		{1},
> > +		{0, 0, 0, 0, 1, 1, 0, 0, 0}
> > +	},
> > +	/* IOTLB and EIOTLB */
> > +	{
> > +		{1, 1, 0, 1, 0, 0, 0, 0, 0},
> > +		{0, 0, 0, 0, 1, 0, 1, 1, 1}
> > +	},
> > +	/* PASID cache */
> > +	{
> > +		{0},
> > +		{0, 0, 0, 0, 1, 1, 0, 0, 0}
> > +	},
> > +	/* context cache */
> > +	{
> > +		{1, 1, 1}
> > +	}
> > +};
> > +
> > +const static u64
> > inv_type_granu_table[IOMMU_INV_NR_TYPE][2][IOMMU_INV_NR_GRANU] = {
> > +	/* extended dev IOTLBs, only global is valid */
> > +	{
> > +		{QI_DEV_IOTLB_GRAN_ALL},
> > +		{0, 0, 0, 0, QI_DEV_IOTLB_GRAN_ALL,
> > QI_DEV_IOTLB_GRAN_PASID_SEL, 0, 0, 0}
> > +	},
> > +	/* IOTLB and EIOTLB */
> > +	{
> > +		{DMA_TLB_GLOBAL_FLUSH, DMA_TLB_DSI_FLUSH, 0,
> > DMA_TLB_PSI_FLUSH},
> > +		{0, 0, 0, 0, QI_GRAN_ALL_ALL, 0, QI_GRAN_NONG_ALL,
> > QI_GRAN_NONG_PASID, QI_GRAN_PSI_PASID}
> > +	},
> > +	/* PASID cache */
> > +	{
> > +		{0},
> > +		{0, 0, 0, 0, QI_PC_ALL_PASIDS, QI_PC_PASID_SEL}
> > +	},
> > +	/* context cache */
> > +	{
> > +		{DMA_CCMD_GLOBAL_INVL, DMA_CCMD_DOMAIN_INVL,
> > DMA_CCMD_DEVICE_INVL}
> > +	}
> > +};
> > +
> > +static inline int to_vtd_granularity(int type, int granu, int
> > with_pasid, u64 *vtd_granu) +{
> > +	if (type >= IOMMU_INV_NR_TYPE || granu >=
> > IOMMU_INV_NR_GRANU || with_pasid > 1)
> > +		return -EINVAL;
> > +
> > +	if (inv_type_granu_map[type][with_pasid][granu] == 0)
> > +		return -EINVAL;
> > +
> > +	*vtd_granu = inv_type_granu_table[type][with_pasid][granu];
> > +
> > +	return 0;
> > +}
> > +
> > +static int intel_iommu_sva_invalidate(struct iommu_domain *domain,
> > +		struct device *dev, struct tlb_invalidate_info
> > *inv_info)  
> 
> inv_info->hdr.version is never checked, why do we have these if
> they're not used?
> 
the version was added to leave room for future extension. you are
right, it should be checked.
> > +{
> > +	struct intel_iommu *iommu;
> > +	struct dmar_domain *dmar_domain = to_dmar_domain(domain);
> > +	struct device_domain_info *info;
> > +	u16 did, sid;
> > +	u8 bus, devfn;
> > +	int ret = 0;
> > +	u64 granu;
> > +	unsigned long flags;
> > +
> > +	if (!inv_info || !dmar_domain)
> > +		return -EINVAL;
> > +
> > +	iommu = device_to_iommu(dev, &bus, &devfn);
> > +	if (!iommu)
> > +		return -ENODEV;
> > +
> > +	if (!dev || !dev_is_pci(dev))
> > +		return -ENODEV;
> > +
> > +	did = dmar_domain->iommu_did[iommu->seq_id];
> > +	sid = PCI_DEVID(bus, devfn);
> > +	ret = to_vtd_granularity(inv_info->hdr.type,
> > inv_info->granularity,
> > +				!!(inv_info->flags &
> > IOMMU_INVALIDATE_PASID_TAGGED), &granu);
> > +	if (ret) {
> > +		pr_err("Invalid range type %d, granu %d\n",
> > inv_info->hdr.type,
> > +			inv_info->granularity);
> > +		return ret;
> > +	}
> > +
> > +	spin_lock(&iommu->lock);
> > +	spin_lock_irqsave(&device_domain_lock, flags);
> > +
> > +	switch (inv_info->hdr.type) {
> > +	case IOMMU_INV_TYPE_CONTEXT:
> > +		iommu->flush.flush_context(iommu, did, sid,
> > +					DMA_CCMD_MASK_NOBIT,
> > granu);
> > +		break;
> > +	case IOMMU_INV_TYPE_TLB:
> > +		/* We need to deal with two scenarios:
> > +		 * - IOTLB for request w/o PASID
> > +		 * - extended IOTLB for request with PASID.
> > +		 */
> > +		if (inv_info->size &&
> > +			(inv_info->addr & ((1 << (VTD_PAGE_SHIFT +
> > inv_info->size)) - 1))) {
> > +			pr_err("Addr out of range, addr 0x%llx,
> > size order %d\n",
> > +				inv_info->addr, inv_info->size);
> > +			ret = -ERANGE;
> > +			goto out_unlock;
> > +		}
> > +
> > +		if (inv_info->flags &
> > IOMMU_INVALIDATE_PASID_TAGGED)
> > +			qi_flush_eiotlb(iommu, did,
> > mm_to_dma_pfn(inv_info->addr),
> > +					inv_info->pasid,
> > +					inv_info->size, granu,
> > +					inv_info->flags &
> > IOMMU_INVALIDATE_GLOBAL_PAGE);
> > +		else
> > +			qi_flush_iotlb(iommu, did,
> > mm_to_dma_pfn(inv_info->addr),
> > +				inv_info->size, granu);
> > +		/**
> > +		 * Always flush device IOTLB if ATS is enabled
> > since guest
> > +		 * vIOMMU exposes CM = 1, no device IOTLB flush
> > will be passed
> > +		 * down.
> > +		 */
> > +		info = iommu_support_dev_iotlb(dmar_domain, iommu,
> > bus, devfn);
> > +		if (info && info->ats_enabled) {
> > +			if (inv_info->flags &
> > IOMMU_INVALIDATE_PASID_TAGGED)
> > +				qi_flush_dev_eiotlb(iommu, sid,
> > +						inv_info->pasid,
> > info->ats_qdep,
> > +						inv_info->addr,
> > inv_info->size,
> > +						granu);
> > +			else
> > +				qi_flush_dev_iotlb(iommu, sid,
> > info->pfsid,
> > +						info->ats_qdep,
> > inv_info->addr,
> > +						inv_info->size);
> > +		}
> > +		break;
> > +	case IOMMU_INV_TYPE_PASID:
> > +		qi_flush_pasid(iommu, did, granu, inv_info->pasid);
> > +
> > +		break;
> > +	default:
> > +		dev_err(dev, "Unknown IOMMU invalidation type
> > %d\n",
> > +			inv_info->hdr.type);
> > +		ret = -EINVAL;
> > +	}  
> 
> 
> More verbose logging,
you mean dev_err is unnecessary? I will remove that.
> is vfio just passing these through allowing them
> to be user reachable?  Thanks,
yes, the invalidation types are in uapi, expect qemu traps invalidation
from vIOMMU and passdown to physical IOMMU.
> 
> Alex
> 
>  [...]  
> 

[Jacob Pan]

WARNING: multiple messages have this Message-ID (diff)
From: Jacob Pan <jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Alex Williamson
	<alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Yi L <yi.l.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
	Raj Ashok <ashok.raj-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Greg Kroah-Hartman
	<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
	Rafael Wysocki
	<rafael.j.wysocki-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
	David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Subject: Re: [PATCH v4 09/22] iommu/vt-d: add svm/sva invalidate function
Date: Fri, 20 Apr 2018 15:36:59 -0700	[thread overview]
Message-ID: <20180420153659.3052139d@jacob-builder> (raw)
In-Reply-To: <20180417131045.7635a63d-DGNDKt5SQtizQB+pC5nmwQ@public.gmane.org>

On Tue, 17 Apr 2018 13:10:45 -0600
Alex Williamson <alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:

> On Mon, 16 Apr 2018 14:48:58 -0700
> Jacob Pan <jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote:
> 
> > When Shared Virtual Address (SVA) is enabled for a guest OS via
> > vIOMMU, we need to provide invalidation support at IOMMU API and
> > driver level. This patch adds Intel VT-d specific function to
> > implement iommu passdown invalidate API for shared virtual address.
> > 
> > The use case is for supporting caching structure invalidation
> > of assigned SVM capable devices. Emulated IOMMU exposes queue
> > invalidation capability and passes down all descriptors from the
> > guest to the physical IOMMU.
> > 
> > The assumption is that guest to host device ID mapping should be
> > resolved prior to calling IOMMU driver. Based on the device handle,
> > host IOMMU driver can replace certain fields before submit to the
> > invalidation queue.
> > 
> > Signed-off-by: Liu, Yi L <yi.l.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
> > Signed-off-by: Ashok Raj <ashok.raj-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > Signed-off-by: Jacob Pan <jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
> > ---
> >  drivers/iommu/intel-iommu.c | 170
> > ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 170
> > insertions(+)
> > 
> > diff --git a/drivers/iommu/intel-iommu.c
> > b/drivers/iommu/intel-iommu.c index cae4042..c765448 100644
> > --- a/drivers/iommu/intel-iommu.c
> > +++ b/drivers/iommu/intel-iommu.c
> > @@ -4973,6 +4973,175 @@ static void
> > intel_iommu_detach_device(struct iommu_domain *domain,
> > dmar_remove_one_dev_info(to_dmar_domain(domain), dev); }
> >  
> > +/*
> > + * 3D array for converting IOMMU generic type-granularity to VT-d
> > granularity
> > + * X indexed by enum iommu_inv_type
> > + * Y indicates request without and with PASID
> > + * Z indexed by enum iommu_inv_granularity
> > + *
> > + * For an example, if we want to find the VT-d granularity
> > encoding for IOTLB
> > + * type, DMA request with PASID, and page selective. The look up
> > indices are:
> > + * [1][1][8], where
> > + * 1: IOMMU_INV_TYPE_TLB
> > + * 1: with PASID
> > + * 8: IOMMU_INV_GRANU_PAGE_PASID
> > + *
> > + * Granu_map array indicates validity of the table. 1: valid, 0:
> > invalid
> > + *
> > + */
> > +const static int
> > inv_type_granu_map[IOMMU_INV_NR_TYPE][2][IOMMU_INV_NR_GRANU] = {
> > +	/* extended dev IOTLBs, for dev-IOTLB, only global is
> > valid,
> > +	   for dev-EXIOTLB, two valid granu */
> > +	{
> > +		{1},
> > +		{0, 0, 0, 0, 1, 1, 0, 0, 0}
> > +	},
> > +	/* IOTLB and EIOTLB */
> > +	{
> > +		{1, 1, 0, 1, 0, 0, 0, 0, 0},
> > +		{0, 0, 0, 0, 1, 0, 1, 1, 1}
> > +	},
> > +	/* PASID cache */
> > +	{
> > +		{0},
> > +		{0, 0, 0, 0, 1, 1, 0, 0, 0}
> > +	},
> > +	/* context cache */
> > +	{
> > +		{1, 1, 1}
> > +	}
> > +};
> > +
> > +const static u64
> > inv_type_granu_table[IOMMU_INV_NR_TYPE][2][IOMMU_INV_NR_GRANU] = {
> > +	/* extended dev IOTLBs, only global is valid */
> > +	{
> > +		{QI_DEV_IOTLB_GRAN_ALL},
> > +		{0, 0, 0, 0, QI_DEV_IOTLB_GRAN_ALL,
> > QI_DEV_IOTLB_GRAN_PASID_SEL, 0, 0, 0}
> > +	},
> > +	/* IOTLB and EIOTLB */
> > +	{
> > +		{DMA_TLB_GLOBAL_FLUSH, DMA_TLB_DSI_FLUSH, 0,
> > DMA_TLB_PSI_FLUSH},
> > +		{0, 0, 0, 0, QI_GRAN_ALL_ALL, 0, QI_GRAN_NONG_ALL,
> > QI_GRAN_NONG_PASID, QI_GRAN_PSI_PASID}
> > +	},
> > +	/* PASID cache */
> > +	{
> > +		{0},
> > +		{0, 0, 0, 0, QI_PC_ALL_PASIDS, QI_PC_PASID_SEL}
> > +	},
> > +	/* context cache */
> > +	{
> > +		{DMA_CCMD_GLOBAL_INVL, DMA_CCMD_DOMAIN_INVL,
> > DMA_CCMD_DEVICE_INVL}
> > +	}
> > +};
> > +
> > +static inline int to_vtd_granularity(int type, int granu, int
> > with_pasid, u64 *vtd_granu) +{
> > +	if (type >= IOMMU_INV_NR_TYPE || granu >=
> > IOMMU_INV_NR_GRANU || with_pasid > 1)
> > +		return -EINVAL;
> > +
> > +	if (inv_type_granu_map[type][with_pasid][granu] == 0)
> > +		return -EINVAL;
> > +
> > +	*vtd_granu = inv_type_granu_table[type][with_pasid][granu];
> > +
> > +	return 0;
> > +}
> > +
> > +static int intel_iommu_sva_invalidate(struct iommu_domain *domain,
> > +		struct device *dev, struct tlb_invalidate_info
> > *inv_info)  
> 
> inv_info->hdr.version is never checked, why do we have these if
> they're not used?
> 
the version was added to leave room for future extension. you are
right, it should be checked.
> > +{
> > +	struct intel_iommu *iommu;
> > +	struct dmar_domain *dmar_domain = to_dmar_domain(domain);
> > +	struct device_domain_info *info;
> > +	u16 did, sid;
> > +	u8 bus, devfn;
> > +	int ret = 0;
> > +	u64 granu;
> > +	unsigned long flags;
> > +
> > +	if (!inv_info || !dmar_domain)
> > +		return -EINVAL;
> > +
> > +	iommu = device_to_iommu(dev, &bus, &devfn);
> > +	if (!iommu)
> > +		return -ENODEV;
> > +
> > +	if (!dev || !dev_is_pci(dev))
> > +		return -ENODEV;
> > +
> > +	did = dmar_domain->iommu_did[iommu->seq_id];
> > +	sid = PCI_DEVID(bus, devfn);
> > +	ret = to_vtd_granularity(inv_info->hdr.type,
> > inv_info->granularity,
> > +				!!(inv_info->flags &
> > IOMMU_INVALIDATE_PASID_TAGGED), &granu);
> > +	if (ret) {
> > +		pr_err("Invalid range type %d, granu %d\n",
> > inv_info->hdr.type,
> > +			inv_info->granularity);
> > +		return ret;
> > +	}
> > +
> > +	spin_lock(&iommu->lock);
> > +	spin_lock_irqsave(&device_domain_lock, flags);
> > +
> > +	switch (inv_info->hdr.type) {
> > +	case IOMMU_INV_TYPE_CONTEXT:
> > +		iommu->flush.flush_context(iommu, did, sid,
> > +					DMA_CCMD_MASK_NOBIT,
> > granu);
> > +		break;
> > +	case IOMMU_INV_TYPE_TLB:
> > +		/* We need to deal with two scenarios:
> > +		 * - IOTLB for request w/o PASID
> > +		 * - extended IOTLB for request with PASID.
> > +		 */
> > +		if (inv_info->size &&
> > +			(inv_info->addr & ((1 << (VTD_PAGE_SHIFT +
> > inv_info->size)) - 1))) {
> > +			pr_err("Addr out of range, addr 0x%llx,
> > size order %d\n",
> > +				inv_info->addr, inv_info->size);
> > +			ret = -ERANGE;
> > +			goto out_unlock;
> > +		}
> > +
> > +		if (inv_info->flags &
> > IOMMU_INVALIDATE_PASID_TAGGED)
> > +			qi_flush_eiotlb(iommu, did,
> > mm_to_dma_pfn(inv_info->addr),
> > +					inv_info->pasid,
> > +					inv_info->size, granu,
> > +					inv_info->flags &
> > IOMMU_INVALIDATE_GLOBAL_PAGE);
> > +		else
> > +			qi_flush_iotlb(iommu, did,
> > mm_to_dma_pfn(inv_info->addr),
> > +				inv_info->size, granu);
> > +		/**
> > +		 * Always flush device IOTLB if ATS is enabled
> > since guest
> > +		 * vIOMMU exposes CM = 1, no device IOTLB flush
> > will be passed
> > +		 * down.
> > +		 */
> > +		info = iommu_support_dev_iotlb(dmar_domain, iommu,
> > bus, devfn);
> > +		if (info && info->ats_enabled) {
> > +			if (inv_info->flags &
> > IOMMU_INVALIDATE_PASID_TAGGED)
> > +				qi_flush_dev_eiotlb(iommu, sid,
> > +						inv_info->pasid,
> > info->ats_qdep,
> > +						inv_info->addr,
> > inv_info->size,
> > +						granu);
> > +			else
> > +				qi_flush_dev_iotlb(iommu, sid,
> > info->pfsid,
> > +						info->ats_qdep,
> > inv_info->addr,
> > +						inv_info->size);
> > +		}
> > +		break;
> > +	case IOMMU_INV_TYPE_PASID:
> > +		qi_flush_pasid(iommu, did, granu, inv_info->pasid);
> > +
> > +		break;
> > +	default:
> > +		dev_err(dev, "Unknown IOMMU invalidation type
> > %d\n",
> > +			inv_info->hdr.type);
> > +		ret = -EINVAL;
> > +	}  
> 
> 
> More verbose logging,
you mean dev_err is unnecessary? I will remove that.
> is vfio just passing these through allowing them
> to be user reachable?  Thanks,
yes, the invalidation types are in uapi, expect qemu traps invalidation
from vIOMMU and passdown to physical IOMMU.
> 
> Alex
> 
>  [...]  
> 

[Jacob Pan]

  reply	other threads:[~2018-04-20 22:36 UTC|newest]

Thread overview: 130+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 21:48 [PATCH v4 00/22] IOMMU and VT-d driver support for Shared Virtual Address (SVA) Jacob Pan
2018-04-16 21:48 ` Jacob Pan
2018-04-16 21:48 ` [PATCH v4 01/22] iommu: introduce bind_pasid_table API function Jacob Pan
2018-04-16 21:48   ` Jacob Pan
2018-04-16 21:48 ` [PATCH v4 02/22] iommu/vt-d: move device_domain_info to header Jacob Pan
2018-04-16 21:48   ` Jacob Pan
2018-04-16 21:48 ` [PATCH v4 03/22] iommu/vt-d: add a flag for pasid table bound status Jacob Pan
2018-04-16 21:48   ` Jacob Pan
2018-04-16 21:48 ` [PATCH v4 04/22] iommu/vt-d: add bind_pasid_table function Jacob Pan
2018-04-16 21:48   ` Jacob Pan
2018-04-17 19:10   ` Alex Williamson
2018-04-17 19:10     ` Alex Williamson
2018-04-20 18:25     ` Jean-Philippe Brucker
2018-04-20 18:25       ` Jean-Philippe Brucker
2018-04-20 23:42       ` Jacob Pan
2018-04-20 23:42         ` Jacob Pan
2018-05-29 20:09         ` Alex Williamson
2018-05-29 20:09           ` Alex Williamson
2018-05-30  1:41           ` Tian, Kevin
2018-05-30  1:41             ` Tian, Kevin
2018-05-30  3:17             ` Alex Williamson
2018-05-30  3:17               ` Alex Williamson
2018-05-30  3:45               ` Tian, Kevin
2018-05-30  3:45                 ` Tian, Kevin
2018-05-30 11:53                 ` Jean-Philippe Brucker
2018-05-30 11:53                   ` Jean-Philippe Brucker
2018-05-30 19:52                   ` Jacob Pan
2018-05-30 19:52                     ` Jacob Pan
2018-05-31  9:09                     ` Jean-Philippe Brucker
2018-05-31  9:09                       ` Jean-Philippe Brucker
2018-06-05 17:32                       ` Jacob Pan
2018-06-06 11:20                         ` Jean-Philippe Brucker
2018-06-06 11:20                           ` Jean-Philippe Brucker
2018-06-06 21:22                           ` Jacob Pan
2018-06-07 13:21                             ` Jean-Philippe Brucker
2018-04-20 23:22     ` Jacob Pan
2018-04-20 23:22       ` Jacob Pan
2018-04-16 21:48 ` [PATCH v4 05/22] iommu: introduce iommu invalidate API function Jacob Pan
2018-04-16 21:48   ` Jacob Pan
2018-04-20 18:19   ` Jean-Philippe Brucker
2018-04-20 18:19     ` Jean-Philippe Brucker
2018-04-23 20:43     ` Jacob Pan
2018-04-23 20:43       ` Jacob Pan
2018-04-27 18:07       ` Jean-Philippe Brucker
2018-04-27 18:07         ` Jean-Philippe Brucker
2018-04-28  2:41         ` Tian, Kevin
2018-04-28  2:41           ` Tian, Kevin
2018-05-01 22:58         ` Jacob Pan
2018-05-01 22:58           ` Jacob Pan
2018-05-02  9:31           ` Jean-Philippe Brucker
2018-05-02  9:31             ` Jean-Philippe Brucker
2018-05-04  4:46             ` Jacob Pan
2018-05-04  4:46               ` Jacob Pan
2018-05-04 18:07               ` Jacob Pan
2018-05-04 18:07                 ` Jacob Pan
2018-05-08 10:35                 ` Jean-Philippe Brucker
2018-05-08 10:35                   ` Jean-Philippe Brucker
2018-05-09 12:55                   ` Jacob Pan
2018-05-09 12:55                     ` Jacob Pan
2018-05-05 22:19   ` Jerry Snitselaar
2018-05-05 22:19     ` Jerry Snitselaar
2018-05-07 15:41     ` Jacob Pan
2018-05-07 15:41       ` Jacob Pan
2018-04-16 21:48 ` [PATCH v4 06/22] iommu/vt-d: add definitions for PFSID Jacob Pan
2018-04-16 21:48   ` Jacob Pan
2018-04-16 21:48 ` [PATCH v4 07/22] iommu/vt-d: fix dev iotlb pfsid use Jacob Pan
2018-04-16 21:48   ` Jacob Pan
2018-04-16 21:48 ` [PATCH v4 08/22] iommu/vt-d: support flushing more translation cache types Jacob Pan
2018-04-16 21:48   ` Jacob Pan
2018-04-16 21:48 ` [PATCH v4 09/22] iommu/vt-d: add svm/sva invalidate function Jacob Pan
2018-04-16 21:48   ` Jacob Pan
2018-04-17 19:10   ` Alex Williamson
2018-04-17 19:10     ` Alex Williamson
2018-04-20 22:36     ` Jacob Pan [this message]
2018-04-20 22:36       ` Jacob Pan
2018-04-16 21:48 ` [PATCH v4 10/22] iommu: introduce device fault data Jacob Pan
2018-04-16 21:48   ` Jacob Pan
2018-04-23 10:11   ` Jean-Philippe Brucker
2018-04-23 10:11     ` Jean-Philippe Brucker
2018-04-23 11:54     ` Jacob Pan
2018-04-23 11:54       ` Jacob Pan
2018-05-20  8:17   ` Liu, Yi L
2018-05-21 23:16     ` Jacob Pan
2018-05-21 23:16       ` Jacob Pan
2018-04-16 21:49 ` [PATCH v4 11/22] driver core: add per device iommu param Jacob Pan
2018-04-16 21:49   ` Jacob Pan
2018-04-23 10:26   ` Greg Kroah-Hartman
2018-04-23 10:26     ` Greg Kroah-Hartman
2018-04-16 21:49 ` [PATCH v4 12/22] iommu: introduce device fault report API Jacob Pan
2018-04-16 21:49   ` Jacob Pan
2018-04-23 11:30   ` Jean-Philippe Brucker
2018-04-23 11:30     ` Jean-Philippe Brucker
2018-04-24 18:29     ` Jacob Pan
2018-04-24 18:29       ` Jacob Pan
2018-04-30 16:53   ` Jean-Philippe Brucker
2018-04-30 16:53     ` Jean-Philippe Brucker
2018-04-30 18:54     ` Jacob Pan
2018-04-16 21:49 ` [PATCH v4 13/22] iommu: introduce page response function Jacob Pan
2018-04-16 21:49   ` Jacob Pan
2018-04-23 11:47   ` Jean-Philippe Brucker
2018-04-23 11:47     ` Jean-Philippe Brucker
2018-04-23 12:16     ` Jacob Pan
2018-04-23 12:16       ` Jacob Pan
2018-04-23 15:50       ` Jean-Philippe Brucker
2018-04-23 15:50         ` Jean-Philippe Brucker
2018-04-16 21:49 ` [PATCH v4 14/22] iommu: handle page response timeout Jacob Pan
2018-04-16 21:49   ` Jacob Pan
2018-04-23 15:36   ` Jean-Philippe Brucker
2018-04-25 15:37     ` Jacob Pan
2018-04-25 15:37       ` Jacob Pan
2018-04-30 10:58       ` Jean-Philippe Brucker
2018-04-30 10:58         ` Jean-Philippe Brucker
2018-04-30 17:54         ` Jacob Pan
2018-04-30 17:54           ` Jacob Pan
2018-04-16 21:49 ` [PATCH v4 15/22] iommu/config: add build dependency for dmar Jacob Pan
2018-04-16 21:49   ` Jacob Pan
2018-04-16 21:49 ` [PATCH v4 16/22] iommu/vt-d: report non-recoverable faults to device Jacob Pan
2018-04-16 21:49   ` Jacob Pan
2018-04-16 21:49 ` [PATCH v4 17/22] iommu/intel-svm: report device page request Jacob Pan
2018-04-16 21:49   ` Jacob Pan
2018-04-16 21:49 ` [PATCH v4 18/22] iommu/intel-svm: replace dev ops with fault report API Jacob Pan
2018-04-16 21:49   ` Jacob Pan
2018-04-16 21:49 ` [PATCH v4 19/22] iommu/intel-svm: do not flush iotlb for viommu Jacob Pan
2018-04-16 21:49   ` Jacob Pan
2018-04-16 21:49 ` [PATCH v4 20/22] iommu/vt-d: add intel iommu page response function Jacob Pan
2018-04-16 21:49   ` Jacob Pan
2018-04-16 21:49 ` [PATCH v4 21/22] trace/iommu: add sva trace events Jacob Pan
2018-04-16 21:49 ` [PATCH v4 22/22] iommu: use sva invalidate and device fault trace event Jacob Pan
  -- strict thread matches above, loose matches on Subject: below --
2018-03-23  3:11 [PATCH v4 00/22] IOMMU and VT-d driver support for Shared Virtual Address (SVA) Jacob Pan
2018-03-23  3:12 ` [PATCH v4 09/22] iommu/vt-d: add svm/sva invalidate function Jacob Pan
2018-03-23  3:12   ` Jacob Pan

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=20180420153659.3052139d@jacob-builder \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=ashok.raj@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jean-philippe.brucker@arm.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=yi.l.liu@intel.com \
    --cc=yi.l.liu@linux.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 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.