dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: daniel.vetter@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, "Michel Dänzer" <michel@daenzer.net>
Subject: Re: [PATCH] dma-buf: fix and rework dma_buf_poll v7
Date: Wed, 22 Sep 2021 13:08:44 +0200	[thread overview]
Message-ID: <9eca7ec8-4a33-4ddb-e4cb-295c1033aa60@gmail.com> (raw)
In-Reply-To: <97ea61fb-aa20-5220-8304-e71145cc7587@daenzer.net>

Totally forgotten to ping once more about that.

Michel has tested this now and I think we should push it ASAP. So can I 
get an rb?

Thanks,
Christian.

Am 23.07.21 um 10:04 schrieb Michel Dänzer:
> On 2021-07-20 3:11 p.m., Christian König wrote:
>> Daniel pointed me towards this function and there are multiple obvious problems
>> in the implementation.
>>
>> First of all the retry loop is not working as intended. In general the retry
>> makes only sense if you grab the reference first and then check the sequence
>> values.
>>
>> Then we should always also wait for the exclusive fence.
>>
>> It's also good practice to keep the reference around when installing callbacks
>> to fences you don't own.
>>
>> And last the whole implementation was unnecessary complex and rather hard to
>> understand which could lead to probably unexpected behavior of the IOCTL.
>>
>> Fix all this by reworking the implementation from scratch. Dropping the
>> whole RCU approach and taking the lock instead.
>>
>> Only mildly tested and needs a thoughtful review of the code.
>>
>> v2: fix the reference counting as well
>> v3: keep the excl fence handling as is for stable
>> v4: back to testing all fences, drop RCU
>> v5: handle in and out separately
>> v6: add missing clear of events
>> v7: change coding style as suggested by Michel, drop unused variables
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> CC: stable@vger.kernel.org
> Working fine with https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1880
>
> Tested-by: Michel Dänzer <mdaenzer@redhat.com>
>
>


  reply	other threads:[~2021-09-22 11:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 13:11 [PATCH] dma-buf: fix and rework dma_buf_poll v7 Christian König
2021-07-23  8:04 ` Michel Dänzer
2021-09-22 11:08   ` Christian König [this message]
2021-09-30  9:00     ` Daniel Vetter
2021-09-30  9:48       ` Christian König
2021-09-30 10:26         ` Daniel Vetter
2021-09-30 11:32           ` Christian König
2021-09-30 14:13             ` Daniel Vetter

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=9eca7ec8-4a33-4ddb-e4cb-295c1033aa60@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=michel@daenzer.net \
    /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