From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
dri-devel@lists.freedesktop.org, lyude@redhat.com
Subject: Re: [PATCH] dma-buf: fix reservation_object_wait_timeout_rcu once more v2
Date: Tue, 23 Jan 2018 09:11:23 +0100 [thread overview]
Message-ID: <2d6e8ffc-694a-db2d-e483-355d2879218b@gmail.com> (raw)
In-Reply-To: <151665178351.21091.18086711879499823249@mail.alporthouse.com>
Am 22.01.2018 um 21:09 schrieb Chris Wilson:
> Quoting Christian König (2018-01-22 20:00:03)
>> We need to set shared_count even if we already have a fence to wait for.
>>
>> v2: init i to -1 as well
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> Cc: stable@vger.kernel.org
>> Tested-by: Lyude Paul <lyude@redhat.com>
>> Reviewed-by: Lyude Paul <lyude@redhat.com>
>> ---
>> drivers/dma-buf/reservation.c | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/dma-buf/reservation.c b/drivers/dma-buf/reservation.c
>> index 461afa9febd4..314eb1071cce 100644
>> --- a/drivers/dma-buf/reservation.c
>> +++ b/drivers/dma-buf/reservation.c
>> @@ -484,13 +484,15 @@ long reservation_object_wait_timeout_rcu(struct reservation_object *obj,
>> unsigned long timeout)
>> {
>> struct dma_fence *fence;
>> - unsigned seq, shared_count, i = 0;
>> + unsigned seq, shared_count;
>> long ret = timeout ? timeout : 1;
>> + int i;
>>
>> retry:
>> shared_count = 0;
>> seq = read_seqcount_begin(&obj->seq);
>> rcu_read_lock();
>> + i = -1;
> Could be before the seqlock, but
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> Are we at the point where just grabbing the snapshot of fences with your
> new get_fences_rcu() returning a single array will be simpler? (It also
> has the change in behaviour of not updating the snapshot across the long
> lived wait.)
Yeah, thought about that as well.
> If you want to avoid the kmalloc, we could teach it populate the
> caller's stack allocated array first.
Something like a helper function which just grabs all fences and puts
them in an array of size n? And if the array is to small we return
-ENOSPC and the caller needs to resize it.
Good idea, putting this on my TODO list, but no idea when I can get
around to actually doing it.
Christian.
> -Chris
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-01-23 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 20:00 [PATCH] dma-buf: fix reservation_object_wait_timeout_rcu once more v2 Christian König
2018-01-22 20:09 ` Chris Wilson
2018-01-23 8:11 ` Christian König [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=2d6e8ffc-694a-db2d-e483-355d2879218b@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lyude@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