From: Alex Williamson <alex.williamson@redhat.com>
To: Bharat Bhushan <Bharat.Bhushan@freescale.com>
Cc: kvm@vger.kernel.org, marc.zyngier@arm.com, will.deacon@arm.com,
kvmarm@lists.cs.columbia.edu
Subject: Re: [RFC PATCH 3/6] vfio: Extend iommu-info to return MSIs automap state
Date: Fri, 02 Oct 2015 16:46:01 -0600 [thread overview]
Message-ID: <1443825961.26107.188.camel@redhat.com> (raw)
In-Reply-To: <1443624989-24346-3-git-send-email-Bharat.Bhushan@freescale.com>
On Wed, 2015-09-30 at 20:26 +0530, Bharat Bhushan wrote:
> This patch allows the user-space to know whether msi-pages
> are automatically mapped with some magic iova or not.
>
> Even if the msi-pages are automatically mapped, still user-space
> wants to over-ride the automatic iova selection for msi-mapping.
> For this user-space need to know whether it is allowed to change
> the automatic mapping or not and this API provides this mechanism.
> Follow up patches will provide how to over-ride this.
>
> Signed-off-by: Bharat Bhushan <Bharat.Bhushan@freescale.com>
> ---
> drivers/vfio/vfio_iommu_type1.c | 32 ++++++++++++++++++++++++++++++++
> include/uapi/linux/vfio.h | 3 +++
> 2 files changed, 35 insertions(+)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index fa5d3e4..3315fb6 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -59,6 +59,7 @@ struct vfio_iommu {
> struct rb_root dma_list;
> bool v2;
> bool nesting;
> + bool allow_msi_reconfig;
> struct list_head reserved_iova_list;
> };
>
> @@ -1117,6 +1118,23 @@ static int vfio_domains_have_iommu_cache(struct vfio_iommu *iommu)
> return ret;
> }
>
> +static
> +int vfio_domains_get_msi_maps(struct vfio_iommu *iommu,
> + struct iommu_domain_msi_maps *msi_maps)
> +{
> + struct vfio_domain *d;
> + int ret;
> +
> + mutex_lock(&iommu->lock);
> + /* All domains have same msi-automap property, pick first */
> + d = list_first_entry(&iommu->domain_list, struct vfio_domain, next);
> + ret = iommu_domain_get_attr(d->domain, DOMAIN_ATTR_MSI_MAPPING,
> + msi_maps);
> + mutex_unlock(&iommu->lock);
> +
> + return ret;
> +}
> +
> static long vfio_iommu_type1_ioctl(void *iommu_data,
> unsigned int cmd, unsigned long arg)
> {
> @@ -1138,6 +1156,8 @@ static long vfio_iommu_type1_ioctl(void *iommu_data,
> }
> } else if (cmd == VFIO_IOMMU_GET_INFO) {
> struct vfio_iommu_type1_info info;
> + struct iommu_domain_msi_maps msi_maps;
> + int ret;
>
> minsz = offsetofend(struct vfio_iommu_type1_info, iova_pgsizes);
>
> @@ -1149,6 +1169,18 @@ static long vfio_iommu_type1_ioctl(void *iommu_data,
>
> info.flags = 0;
>
> + ret = vfio_domains_get_msi_maps(iommu, &msi_maps);
> + if (ret)
> + return ret;
And now ioctl(VFIO_IOMMU_GET_INFO) no longer works for any IOMMU
implementing domain_get_attr but not supporting DOMAIN_ATTR_MSI_MAPPING.
> +
> + if (msi_maps.override_automap) {
> + info.flags |= VFIO_IOMMU_INFO_MSI_ALLOW_RECONFIG;
> + iommu->allow_msi_reconfig = true;
> + }
> +
> + if (msi_maps.automap)
> + info.flags |= VFIO_IOMMU_INFO_MSI_AUTOMAP;
> +
> info.iova_pgsizes = vfio_pgsize_bitmap(iommu);
>
> return copy_to_user((void __user *)arg, &info, minsz);
> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
> index 1abd1a9..9998f6e 100644
> --- a/include/uapi/linux/vfio.h
> +++ b/include/uapi/linux/vfio.h
> @@ -391,6 +391,9 @@ struct vfio_iommu_type1_info {
> __u32 argsz;
> __u32 flags;
> #define VFIO_IOMMU_INFO_PGSIZES (1 << 0) /* supported page sizes info */
> +#define VFIO_IOMMU_INFO_MSI_AUTOMAP (1 << 1) /* MSI pages are auto-mapped
> + in iommu */
> +#define VFIO_IOMMU_INFO_MSI_ALLOW_RECONFIG (1 << 2) /* Allows reconfig automap*/
> __u64 iova_pgsizes; /* Bitmap of supported page sizes */
> };
>
Once again, exposing interfaces to the user before they actually do
anything is backwards.
next prev parent reply other threads:[~2015-10-02 22:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 14:56 [RFC PATCH 1/6] vfio: Add interface for add/del reserved iova region Bharat Bhushan
2015-09-30 14:56 ` [RFC PATCH 2/6] iommu: Add interface to get msi-pages mapping attributes Bharat Bhushan
2015-09-30 14:56 ` Bharat Bhushan
2015-10-02 22:45 ` Alex Williamson
2015-10-05 5:17 ` Bhushan Bharat
2015-10-05 5:56 ` Bhushan Bharat
2015-09-30 14:56 ` [RFC PATCH 3/6] vfio: Extend iommu-info to return MSIs automap state Bharat Bhushan
2015-09-30 14:56 ` Bharat Bhushan
2015-10-02 22:46 ` Alex Williamson [this message]
2015-10-05 6:00 ` Bhushan Bharat
2015-10-05 22:45 ` Alex Williamson
2015-10-06 8:53 ` Bhushan Bharat
2015-10-06 15:11 ` Alex Williamson
2015-09-30 14:56 ` [RFC PATCH 4/6] vfio: Add interface to iommu-map/unmap MSI pages Bharat Bhushan
2015-09-30 14:56 ` Bharat Bhushan
2015-10-02 22:46 ` Alex Williamson
2015-10-05 6:27 ` Bhushan Bharat
2015-10-05 22:45 ` Alex Williamson
2015-10-06 9:05 ` Bhushan Bharat
2015-10-06 15:12 ` Alex Williamson
2015-09-30 14:56 ` [RFC PATCH 5/6] vfio-pci: Create iommu mapping for msi interrupt Bharat Bhushan
2015-09-30 14:56 ` Bharat Bhushan
2015-09-30 11:02 ` kbuild test robot
2015-09-30 11:02 ` kbuild test robot
2015-09-30 11:32 ` Bhushan Bharat
2015-09-30 11:34 ` kbuild test robot
2015-09-30 11:34 ` kbuild test robot
2015-10-02 22:46 ` Alex Williamson
2015-10-05 7:20 ` Bhushan Bharat
2015-10-05 22:44 ` Alex Williamson
2015-10-06 8:32 ` Bhushan Bharat
2015-10-06 15:06 ` Alex Williamson
2015-09-30 14:56 ` [RFC PATCH 6/6] arm-smmu: Allow to set iommu mapping for MSI Bharat Bhushan
2015-09-30 14:56 ` Bharat Bhushan
2015-10-02 22:46 ` Alex Williamson
2015-10-05 8:33 ` Bhushan Bharat
2015-10-05 22:54 ` Alex Williamson
2015-10-06 10:26 ` Bhushan Bharat
2015-10-26 15:40 ` Christoffer Dall
2015-11-02 2:53 ` Pranavkumar Sawargaonkar
2015-10-02 22:45 ` [RFC PATCH 1/6] vfio: Add interface for add/del reserved iova region Alex Williamson
2015-10-05 4:55 ` Bhushan Bharat
2015-10-05 22:45 ` Alex Williamson
2015-10-06 9:39 ` Bhushan Bharat
2015-10-06 15:21 ` Alex Williamson
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=1443825961.26107.188.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=Bharat.Bhushan@freescale.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=will.deacon@arm.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.