qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: "Liu, Yi L" <yi.l.liu@intel.com>
Cc: kvm@vger.kernel.org, iommu@lists.linux-foundation.org,
	peterx@redhat.com, jasowang@redhat.com, qemu-devel@nongnu.org,
	kevin.tian@intel.com, ashok.raj@intel.com,
	jacob.jun.pan@intel.com, tianyu.lan@intel.com,
	jean-philippe.brucker@arm.com, "Liu,
	Yi L" <yi.l.liu@linux.intel.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: Re: [Qemu-devel] [RFC PATCH 3/8] iommu: Introduce iommu do invalidate API function
Date: Fri, 12 May 2017 15:59:24 -0600	[thread overview]
Message-ID: <20170512155924.755ee17f@t450s.home> (raw)
In-Reply-To: <1493201525-14418-4-git-send-email-yi.l.liu@intel.com>

On Wed, 26 Apr 2017 18:12:00 +0800
"Liu, Yi L" <yi.l.liu@intel.com> wrote:

> From: "Liu, Yi L" <yi.l.liu@linux.intel.com>
> 
> When a SVM capable device is assigned to a guest, the first level page
> tables are owned by the guest and the guest PASID table pointer is
> linked to the device context entry of the physical IOMMU.
> 
> Host IOMMU driver has no knowledge of caching structure updates unless
> the guest invalidation activities are passed down to the host. The
> primary usage is derived from emulated IOMMU in the guest, where QEMU
> can trap invalidation activities before pass them down the
> host/physical IOMMU. There are IOMMU architectural specific actions
> need to be taken which requires the generic APIs introduced in this
> patch to have opaque data in the tlb_invalidate_info argument.
> 
> Signed-off-by: Liu, Yi L <yi.l.liu@linux.intel.com>
> Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
> ---
>  drivers/iommu/iommu.c | 13 +++++++++++++
>  include/linux/iommu.h | 16 ++++++++++++++++
>  2 files changed, 29 insertions(+)
> 
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index f2da636..ca7cff2 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -1153,6 +1153,19 @@ int iommu_unbind_pasid_table(struct iommu_domain *domain, struct device *dev)
>  }
>  EXPORT_SYMBOL_GPL(iommu_unbind_pasid_table);
>  
> +int iommu_do_invalidate(struct iommu_domain *domain,
> +		struct device *dev, struct tlb_invalidate_info *inv_info)
> +{
> +	int ret = 0;
> +
> +	if (unlikely(domain->ops->do_invalidate == NULL))
> +		return -ENODEV;
> +
> +	ret = domain->ops->do_invalidate(domain, dev, inv_info);
> +	return ret;

nit, ret is unnecessary.

> +}
> +EXPORT_SYMBOL_GPL(iommu_do_invalidate);
> +
>  static void __iommu_detach_device(struct iommu_domain *domain,
>  				  struct device *dev)
>  {
> diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> index 491a011..a48e3b75 100644
> --- a/include/linux/iommu.h
> +++ b/include/linux/iommu.h
> @@ -140,6 +140,11 @@ struct pasid_table_info {
>  	__u8	opaque[];/* IOMMU-specific details */
>  };
>  
> +struct tlb_invalidate_info {
> +	__u32	model;
> +	__u8	opaque[];
> +};

I'm wondering if 'model' is really necessary here, shouldn't this
function only be called if a bind_pasid_table() succeeded, and then the
model would be set at that time?

This also needs to be uapi since you're expecting a user to provide it
to vfio.  The opaque data needs to be fully specified (relative to
uapi) per model.

> +
>  #ifdef CONFIG_IOMMU_API
>  
>  /**
> @@ -215,6 +220,8 @@ struct iommu_ops {
>  				struct pasid_table_info *pasidt_binfo);
>  	int (*unbind_pasid_table)(struct iommu_domain *domain,
>  				struct device *dev);
> +	int (*do_invalidate)(struct iommu_domain *domain,
> +		struct device *dev, struct tlb_invalidate_info *inv_info);
>  
>  	unsigned long pgsize_bitmap;
>  };
> @@ -240,6 +247,9 @@ extern int iommu_bind_pasid_table(struct iommu_domain *domain,
>  		struct device *dev, struct pasid_table_info *pasidt_binfo);
>  extern int iommu_unbind_pasid_table(struct iommu_domain *domain,
>  				struct device *dev);
> +extern int iommu_do_invalidate(struct iommu_domain *domain,
> +		struct device *dev, struct tlb_invalidate_info *inv_info);
> +
>  extern struct iommu_domain *iommu_get_domain_for_dev(struct device *dev);
>  extern int iommu_map(struct iommu_domain *domain, unsigned long iova,
>  		     phys_addr_t paddr, size_t size, int prot);
> @@ -626,6 +636,12 @@ int iommu_unbind_pasid_table(struct iommu_domain *domain, struct device *dev)
>  	return -EINVAL;
>  }
>  
> +static inline int iommu_do_invalidate(struct iommu_domain *domain,
> +		struct device *dev, struct tlb_invalidate_info *inv_info)
> +{
> +	return -EINVAL;
> +}
> +
>  #endif /* CONFIG_IOMMU_API */
>  
>  #endif /* __LINUX_IOMMU_H */

  reply	other threads:[~2017-05-12 21:59 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 10:11 [Qemu-devel] [RFC PATCH 0/8] Shared Virtual Memory virtualization for VT-d Liu, Yi L
2017-04-26 10:11 ` [Qemu-devel] [RFC PATCH 1/8] iommu: Introduce bind_pasid_table API function Liu, Yi L
2017-04-26 16:56   ` Jean-Philippe Brucker
2017-04-26 18:29     ` jacob pan
2017-04-26 18:59       ` Jean-Philippe Brucker
2017-04-27  6:36     ` Liu, Yi L
2017-04-27 10:12       ` Jean-Philippe Brucker
2017-04-28  7:59         ` Liu, Yi L
2017-04-28  9:04     ` Liu, Yi L
2017-04-28 12:51       ` Jean-Philippe Brucker
2017-05-23  7:50         ` Liu, Yi L
2017-05-25 12:33           ` Jean-Philippe Brucker
2017-05-12 21:59   ` Alex Williamson
2017-05-14 10:56     ` Liu, Yi L
2017-04-26 10:11 ` [Qemu-devel] [RFC PATCH 2/8] iommu/vt-d: add bind_pasid_table function Liu, Yi L
2017-05-12 21:59   ` Alex Williamson
2017-05-15 13:14     ` jacob pan
2017-04-26 10:12 ` [Qemu-devel] [RFC PATCH 3/8] iommu: Introduce iommu do invalidate API function Liu, Yi L
2017-05-12 21:59   ` Alex Williamson [this message]
2017-05-17 10:23     ` Liu, Yi L
2017-04-26 10:12 ` [Qemu-devel] [RFC PATCH 4/8] iommu/vt-d: Add iommu do invalidate function Liu, Yi L
2017-05-12 21:59   ` Alex Williamson
2017-05-17 10:24     ` Liu, Yi L
2017-04-26 10:12 ` [Qemu-devel] [RFC PATCH 5/8] VFIO: Add new IOTCL for PASID Table bind propagation Liu, Yi L
2017-04-26 16:56   ` Jean-Philippe Brucker
2017-04-27  5:43     ` Liu, Yi L
2017-05-11 10:29   ` Liu, Yi L
2017-05-12 21:58   ` Alex Williamson
2017-05-17 10:27     ` Liu, Yi L
2017-05-18 11:29       ` Jean-Philippe Brucker
2017-04-26 10:12 ` [Qemu-devel] [RFC PATCH 6/8] VFIO: do pasid table binding Liu, Yi L
2017-05-09  7:55   ` Xiao Guangrong
2017-05-11 10:29     ` Liu, Yi L
2017-05-12 21:59   ` Alex Williamson
2017-04-26 10:12 ` [Qemu-devel] [RFC PATCH 7/8] VFIO: Add new IOCTL for IOMMU TLB invalidate propagation Liu, Yi L
2017-05-12 12:11   ` Jean-Philippe Brucker
2017-05-14 10:12     ` Liu, Yi L
2017-05-15 12:14       ` Jean-Philippe Brucker
2017-07-02 10:06     ` Liu, Yi L
2017-07-03 11:52       ` Jean-Philippe Brucker
2017-07-03 10:31         ` Liu, Yi L
2017-07-05  6:45           ` Tian, Kevin
2017-07-05 12:42             ` Jean-Philippe Brucker
2017-07-05 17:28               ` Alex Williamson
2017-07-05 22:26                 ` Tian, Kevin
2017-07-14  8:58                 ` Liu, Yi L
2017-07-14 18:15                   ` Alex Williamson
2017-07-17 10:58                     ` Liu, Yi L
2017-07-17 22:45                       ` Alex Williamson
2017-07-18  9:38                         ` Jean-Philippe Brucker
2017-07-18 14:29                           ` Alex Williamson
2017-07-18 15:03                             ` Jean-Philippe Brucker
2017-07-19 10:45                         ` Liu, Yi L
2017-07-19 21:50                           ` Jacob Pan
2017-07-05 22:31               ` Tian, Kevin
2017-05-12 21:58   ` Alex Williamson
2017-05-14 10:55     ` Liu, Yi L
2017-07-05  5:32       ` Tian, Kevin
2017-04-26 10:12 ` [Qemu-devel] [RFC PATCH 8/8] VFIO: do IOMMU TLB invalidation from guest Liu, Yi L
2017-05-08  4:09 ` [Qemu-devel] [RFC PATCH 0/8] Shared Virtual Memory virtualization for VT-d Xiao Guangrong
2017-05-07  7:33   ` Liu, Yi L

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=20170512155924.755ee17f@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=ashok.raj@intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jacob.jun.pan@intel.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=jasowang@redhat.com \
    --cc=jean-philippe.brucker@arm.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tianyu.lan@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 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).