From: Auger Eric <eric.auger@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: fam@euphon.net, lvivier@redhat.com, cohuck@redhat.com,
qemu-devel@nongnu.org, mreitz@redhat.com,
alex.williamson@redhat.com, qemu-arm@nongnu.org,
kwolf@redhat.com, philmd@redhat.com, eric.auger.pro@gmail.com
Subject: Re: [PATCH v2 2/2] util/vfio-helpers: Rework the IOVA allocator to avoid IOVA reserved regions
Date: Tue, 29 Sep 2020 21:44:48 +0200 [thread overview]
Message-ID: <6ebdb1f7-792b-6fbe-d4b3-f06aafc8deef@redhat.com> (raw)
In-Reply-To: <20200929155951.GB191675@stefanha-x1.localdomain>
Hi Stefan,
On 9/29/20 5:59 PM, Stefan Hajnoczi wrote:
> On Tue, Sep 29, 2020 at 10:55:50AM +0200, Eric Auger wrote:
>> diff --git a/util/vfio-helpers.c b/util/vfio-helpers.c
>> index ba0ee6e21c..71145970f3 100644
>> --- a/util/vfio-helpers.c
>> +++ b/util/vfio-helpers.c
>> @@ -667,6 +667,50 @@ static bool qemu_vfio_verify_mappings(QEMUVFIOState *s)
>> return true;
>> }
>>
>> +static int
>> +qemu_vfio_find_fixed_iova(QEMUVFIOState *s, size_t size, uint64_t *iova)
>> +{
>> + int i;
>> +
>> + for (i = 0; i < s->nb_iova_ranges; i++) {
>> + if (s->usable_iova_ranges[i].end < s->low_water_mark) {
>> + continue;
>> + }
>> + s->low_water_mark =
>> + MAX(s->low_water_mark, s->usable_iova_ranges[i].start);
>> +
>> + if (s->usable_iova_ranges[i].end - s->low_water_mark + 1 >= size ||
>> + s->usable_iova_ranges[i].end - s->low_water_mark + 1 == 0) {
>
> I don't understand the == 0 case. It seems like we are allocating an
> IOVA beyond usable_iova_ranges[i].end?>
It is meant to handle the case were low_water_mark = 0 and
s->usable_iova_ranges[0].end = ULLONG_MAX (I know it cannot exist at the
moment but may happen in the future) where we get an overflow. Given the
if (s->usable_iova_ranges[i].end < s->low_water_mark) {
continue;
}
I think this prevents us from allocating beyond
usable_iova_ranges[i].end or do I miss something?
Thanks
Eric
next prev parent reply other threads:[~2020-09-29 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 8:55 [PATCH v2 0/2] NVMe passthrough: Take into account host IOVA reserved regions Eric Auger
2020-09-29 8:55 ` [PATCH v2 1/2] util/vfio-helpers: Collect " Eric Auger
2020-09-29 8:55 ` [PATCH v2 2/2] util/vfio-helpers: Rework the IOVA allocator to avoid " Eric Auger
2020-09-29 15:59 ` Stefan Hajnoczi
2020-09-29 19:44 ` Auger Eric [this message]
2020-09-30 9:18 ` Stefan Hajnoczi
2020-09-30 9:23 ` [PATCH v2 0/2] NVMe passthrough: Take into account host " Stefan Hajnoczi
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=6ebdb1f7-792b-6fbe-d4b3-f06aafc8deef@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).