From: Auger Eric <eric.auger@redhat.com>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
alex.williamson@redhat.com, pmorel@linux.vnet.ibm.com
Cc: kevin.tian@intel.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, xuwei5@hisilicon.com,
linuxarm@huawei.com, iommu@lists.linux-foundation.org
Subject: Re: [PATCH v7 3/6] vfio/type1: Update iova list on detach
Date: Sun, 7 Jul 2019 17:03:14 +0200 [thread overview]
Message-ID: <3bab52b1-da0f-10fe-34e4-889c74e3caad@redhat.com> (raw)
In-Reply-To: <20190626151248.11776-4-shameerali.kolothum.thodi@huawei.com>
Hi Shameer,
On 6/26/19 5:12 PM, Shameer Kolothum wrote:
> Get a copy of iova list on _group_detach and try to update the list.
> On success replace the current one with the copy. Leave the list as
> it is if update fails.
>
> Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> ---
> drivers/vfio/vfio_iommu_type1.c | 91 +++++++++++++++++++++++++++++++++
> 1 file changed, 91 insertions(+)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index b6bfdfa16c33..e872fb3a0f39 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -1873,12 +1873,88 @@ static void vfio_sanity_check_pfn_list(struct vfio_iommu *iommu)
> WARN_ON(iommu->notifier.head);
> }
>
> +/*
> + * Called when a domain is removed in detach. It is possible that
> + * the removed domain decided the iova aperture window. Modify the
> + * iova aperture with the smallest window among existing domains.
> + */
> +static void vfio_iommu_aper_expand(struct vfio_iommu *iommu,
> + struct list_head *iova_copy)
Maybe you could just remove iova_copy for the args and return start,
size. See comment below.
> +{
> + struct vfio_domain *domain;
> + struct iommu_domain_geometry geo;
> + struct vfio_iova *node;
> + dma_addr_t start = 0;
> + dma_addr_t end = (dma_addr_t)~0;
> +
> + list_for_each_entry(domain, &iommu->domain_list, next) {
> + iommu_domain_get_attr(domain->domain, DOMAIN_ATTR_GEOMETRY,
> + &geo);
> + if (geo.aperture_start > start)
> + start = geo.aperture_start;
> + if (geo.aperture_end < end)
> + end = geo.aperture_end;
> + }
> +
> + /* Modify aperture limits. The new aper is either same or bigger */
> + node = list_first_entry(iova_copy, struct vfio_iova, list);
> + node->start = start;
> + node = list_last_entry(iova_copy, struct vfio_iova, list);
> + node->end = end;
> +}
> +
> +/*
> + * Called when a group is detached. The reserved regions for that
> + * group can be part of valid iova now. But since reserved regions
> + * may be duplicated among groups, populate the iova valid regions
> + * list again.
> + */
> +static int vfio_iommu_resv_refresh(struct vfio_iommu *iommu,
> + struct list_head *iova_copy)
> +{
> + struct vfio_domain *d;
> + struct vfio_group *g;
> + struct vfio_iova *node;
> + dma_addr_t start, end;
> + LIST_HEAD(resv_regions);
> + int ret;
> +
> + list_for_each_entry(d, &iommu->domain_list, next) {
> + list_for_each_entry(g, &d->group_list, next)
> + iommu_get_group_resv_regions(g->iommu_group,
> + &resv_regions);
> + }
> +
> + if (list_empty(&resv_regions))
> + return 0;
vfio_iommu_aper_expand() just extended the start/end of first & last
node respectively. In case the iova_copy() featured excluded resv
regions before and now you don't have any anymore, the previous holes
will stay if I don't miss anything?
You may unconditionally recompute start/end, free the copy,
aper_resize() with new start/end and exclude resv regions again?
Thanks
Eric
> +
> + node = list_first_entry(iova_copy, struct vfio_iova, list);
> + start = node->start;
> + node = list_last_entry(iova_copy, struct vfio_iova, list);
> + end = node->end;
> +
> + /* purge the iova list and create new one */
> + vfio_iommu_iova_free(iova_copy);
> +
> + ret = vfio_iommu_aper_resize(iova_copy, start, end);
> + if (ret)
> + goto done;
> +
> + /* Exclude current reserved regions from iova ranges */
> + ret = vfio_iommu_resv_exclude(iova_copy, &resv_regions);
> +done:
> + vfio_iommu_resv_free(&resv_regions);
> + return ret;
> +}
> +
> static void vfio_iommu_type1_detach_group(void *iommu_data,
> struct iommu_group *iommu_group)
> {
> struct vfio_iommu *iommu = iommu_data;
> struct vfio_domain *domain;
> struct vfio_group *group;
> + bool iova_copy_fail;
> + LIST_HEAD(iova_copy);
>
> mutex_lock(&iommu->lock);
>
> @@ -1901,6 +1977,12 @@ static void vfio_iommu_type1_detach_group(void *iommu_data,
> }
> }
>
> + /*
> + * Get a copy of iova list. If success, use copy to update the
> + * list and to replace the current one.
> + */
> + iova_copy_fail = !!vfio_iommu_iova_get_copy(iommu, &iova_copy);
> +
> list_for_each_entry(domain, &iommu->domain_list, next) {
> group = find_iommu_group(domain, iommu_group);
> if (!group)
> @@ -1926,10 +2008,19 @@ static void vfio_iommu_type1_detach_group(void *iommu_data,
> iommu_domain_free(domain->domain);
> list_del(&domain->next);
> kfree(domain);
> + if (!iova_copy_fail && !list_empty(&iommu->domain_list))
> + vfio_iommu_aper_expand(iommu, &iova_copy);
> }
> break;
> }
>
> + if (!iova_copy_fail && !list_empty(&iommu->domain_list)) {
> + if (!vfio_iommu_resv_refresh(iommu, &iova_copy))
> + vfio_iommu_iova_insert_copy(iommu, &iova_copy);
> + else
> + vfio_iommu_iova_free(&iova_copy);
> + }
> +
> detach_group_done:
> mutex_unlock(&iommu->lock);
> }
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-07-07 15:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 15:12 [PATCH v7 0/6] vfio/type1: Add support for valid iova list management Shameer Kolothum
2019-06-26 15:12 ` [PATCH v7 1/6] vfio/type1: Introduce iova list and add iommu aperture validity check Shameer Kolothum
2019-07-03 20:34 ` Alex Williamson
2019-07-04 12:36 ` Shameerali Kolothum Thodi
2019-07-07 15:02 ` Auger Eric
2019-07-08 7:07 ` Shameerali Kolothum Thodi
2019-06-26 15:12 ` [PATCH v7 2/6] vfio/type1: Check reserve region conflict and update iova list Shameer Kolothum
2019-07-03 20:34 ` Alex Williamson
2019-07-04 12:51 ` Shameerali Kolothum Thodi
2019-07-05 12:09 ` Auger Eric
2019-07-08 6:59 ` Shameerali Kolothum Thodi
2019-07-04 22:06 ` Shameerali Kolothum Thodi
2019-07-07 15:02 ` Auger Eric
2019-06-26 15:12 ` [PATCH v7 3/6] vfio/type1: Update iova list on detach Shameer Kolothum
2019-07-03 20:34 ` Alex Williamson
2019-07-04 12:53 ` Shameerali Kolothum Thodi
2019-07-07 15:03 ` Auger Eric [this message]
2019-07-08 7:10 ` Shameerali Kolothum Thodi
2019-06-26 15:12 ` [PATCH v7 4/6] vfio/type1: check dma map request is within a valid iova range Shameer Kolothum
2019-07-07 15:03 ` Auger Eric
2019-06-26 15:12 ` [PATCH v7 5/6] vfio/type1: Add IOVA range capability support Shameer Kolothum
2019-07-07 15:03 ` Auger Eric
2019-06-26 15:12 ` [PATCH v7 6/6] vfio/type1: remove duplicate retrieval of reserved regions Shameer Kolothum
2019-07-07 15:03 ` Auger Eric
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=3bab52b1-da0f-10fe-34e4-889c74e3caad@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=xuwei5@hisilicon.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