From: Alex Williamson <alex.williamson@redhat.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Cc: "eric.auger@redhat.com" <eric.auger@redhat.com>,
"pmorel@linux.vnet.ibm.com" <pmorel@linux.vnet.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>,
John Garry <john.garry@huawei.com>,
"xuwei (O)" <xuwei5@huawei.com>
Subject: Re: [RFC v2 2/5] vfio/type1: Check reserve region conflict and update iova list
Date: Fri, 19 Jan 2018 08:45:34 -0700 [thread overview]
Message-ID: <20180119084534.4b0fbee1@w520.home> (raw)
In-Reply-To: <5FC3163CFD30C246ABAA99954A238FA83863BC04@FRAEML521-MBX.china.huawei.com>
On Fri, 19 Jan 2018 09:48:22 +0000
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com> wrote:
> > > +static void vfio_iommu_iova_resv_refresh(struct vfio_iommu *iommu)
> > > +{
> > > + struct vfio_domain *d;
> > > + struct vfio_group *g;
> > > + struct vfio_iova *node, *tmp;
> > > + struct iommu_resv_region *resv, *resv_next;
> > > + struct list_head resv_regions;
> > > + phys_addr_t start, end;
> > > +
> > > + INIT_LIST_HEAD(&resv_regions);
> > > +
> > > + 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;
> > > +
> > > + list_sort(NULL, &resv_regions, vfio_resv_cmp);
> > > +
> > > + node = list_first_entry(&iommu->iova_list, struct vfio_iova, list);
> > > + start = node->start;
> > > + node = list_last_entry(&iommu->iova_list, struct vfio_iova, list);
> > > + end = node->end;
> >
> > list_sort() only sorts based on ->start, we added reserved regions for
> > all our groups to one list, we potentially have multiple entries with
> > the same ->start. How can we be sure that the last one in the list
> > actually has the largest ->end value?
>
> Hmm.. the sorting is done on the reserved list. The start and end entries
> are of the iova list which is kept updated on _attach(). So I don't think
> there is a problem here.
Oops, yes you're right. List confusion. Thanks,
Alex
next prev parent reply other threads:[~2018-01-19 15:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 16:45 [RFC v2 0/5] vfio/type1: Add support for valid iova list management Shameer Kolothum
2018-01-12 16:45 ` [RFC v2 1/5] vfio/type1: Introduce iova list and add iommu aperture validity check Shameer Kolothum
2018-01-18 0:04 ` Alex Williamson
2018-01-19 9:47 ` Shameerali Kolothum Thodi
2018-01-23 8:25 ` Auger Eric
2018-01-23 10:04 ` Shameerali Kolothum Thodi
2018-01-23 11:20 ` Auger Eric
2018-01-12 16:45 ` [RFC v2 2/5] vfio/type1: Check reserve region conflict and update iova list Shameer Kolothum
2018-01-18 0:04 ` Alex Williamson
2018-01-19 9:48 ` Shameerali Kolothum Thodi
2018-01-19 15:45 ` Alex Williamson [this message]
2018-01-23 8:32 ` Auger Eric
2018-01-23 12:16 ` Shameerali Kolothum Thodi
2018-01-23 12:51 ` Auger Eric
2018-01-23 15:26 ` Shameerali Kolothum Thodi
2018-01-12 16:45 ` [RFC v2 3/5] vfio/type1: check dma map request is within a valid iova range Shameer Kolothum
2018-01-23 8:38 ` Auger Eric
2018-01-12 16:45 ` [RFC v2 4/5] vfio/type1: Add IOVA range capability support Shameer Kolothum
2018-01-23 11:16 ` Auger Eric
2018-01-23 12:51 ` Shameerali Kolothum Thodi
2018-01-12 16:45 ` [RFC v2 5/5] vfio/type1: remove duplicate retrieval of reserved regions Shameer Kolothum
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=20180119084534.4b0fbee1@w520.home \
--to=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=john.garry@huawei.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@huawei.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).