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: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, linuxarm@huawei.com,
john.garry@huawei.com, xuwei5@hisilicon.com,
kevin.tian@intel.com
Subject: Re: [PATCH v7 6/6] vfio/type1: remove duplicate retrieval of reserved regions
Date: Sun, 7 Jul 2019 17:03:47 +0200 [thread overview]
Message-ID: <7e4fd6c4-ac01-1378-cf8d-35ef490fe7ca@redhat.com> (raw)
In-Reply-To: <20190626151248.11776-7-shameerali.kolothum.thodi@huawei.com>
Hi Shameer,
On 6/26/19 5:12 PM, Shameer Kolothum wrote:
> As we now already have the reserved regions list, just pass that into
> vfio_iommu_has_sw_msi() fn.
>
> Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Thanks
Eric
> ---
> drivers/vfio/vfio_iommu_type1.c | 15 ++++++---------
> 1 file changed, 6 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index 450081802dcd..43b1e68ebce9 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -1308,15 +1308,13 @@ static struct vfio_group *find_iommu_group(struct vfio_domain *domain,
> return NULL;
> }
>
> -static bool vfio_iommu_has_sw_msi(struct iommu_group *group, phys_addr_t *base)
> +static bool vfio_iommu_has_sw_msi(struct list_head *group_resv_regions,
> + phys_addr_t *base)
> {
> - struct list_head group_resv_regions;
> - struct iommu_resv_region *region, *next;
> + struct iommu_resv_region *region;
> bool ret = false;
>
> - INIT_LIST_HEAD(&group_resv_regions);
> - iommu_get_group_resv_regions(group, &group_resv_regions);
> - list_for_each_entry(region, &group_resv_regions, list) {
> + list_for_each_entry(region, group_resv_regions, list) {
> /*
> * The presence of any 'real' MSI regions should take
> * precedence over the software-managed one if the
> @@ -1332,8 +1330,7 @@ static bool vfio_iommu_has_sw_msi(struct iommu_group *group, phys_addr_t *base)
> ret = true;
> }
> }
> - list_for_each_entry_safe(region, next, &group_resv_regions, list)
> - kfree(region);
> +
> return ret;
> }
>
> @@ -1774,7 +1771,7 @@ static int vfio_iommu_type1_attach_group(void *iommu_data,
> if (ret)
> goto out_detach;
>
> - resv_msi = vfio_iommu_has_sw_msi(iommu_group, &resv_msi_base);
> + resv_msi = vfio_iommu_has_sw_msi(&group_resv_regions, &resv_msi_base);
>
> INIT_LIST_HEAD(&domain->group_list);
> list_add(&group->next, &domain->group_list);
>
prev parent reply other threads:[~2019-07-07 15:03 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
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 [this message]
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=7e4fd6c4-ac01-1378-cf8d-35ef490fe7ca@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=john.garry@huawei.com \
--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