Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH 7/8] dma-buf: add reservation_object_fences helper
Date: Wed, 7 Aug 2019 11:06:57 +0200	[thread overview]
Message-ID: <7dfbf200-2cee-ac38-0063-fded38d7809e@gmail.com> (raw)
In-Reply-To: <156511947882.6198.3242911017545657039@skylake-alporthouse-com>

Am 06.08.19 um 21:24 schrieb Chris Wilson:
> Quoting Christian König (2019-08-06 16:01:33)
>> Add a new helper to get a consistent set of pointers from the reservation
>> object. While at it group all access helpers together in the header file.
> Ah, needs to be earlier :)

Ah, crap. That got incorrectly reordered while moving the fixes to the 
beginning of the set.

>   
>> +/**
>> + * reservation_object_fences - read consistent fence pointers
>> + * @obj: reservation object where we get the fences from
>> + * @excl: pointer for the exclusive fence
>> + * @list: pointer for the shared fence list
>> + *
>> + * Make sure we have a consisten exclusive fence and shared fence list.
>> + * Must be called with rcu read side lock held.
>> + */
>> +static inline void
>> +reservation_object_fences(struct reservation_object *obj,
>> +                         struct dma_fence **excl,
>> +                         struct reservation_object_list **list)
>> +{
>> +       unsigned int seq;
>> +
>> +       do {
>> +               seq = read_seqcount_begin(&obj->seq);
>> +               *excl = rcu_dereference(obj->fence_excl);
>> +               *list = rcu_dereference(obj->fence);
>> +       } while (read_seqcount_retry(&obj->seq, seq));
>> +}
> I would personally prefer return excl rather than have it as a second
> outparam, but I'd leave that to gcc to decide.
>
> Having stared at this, I agree this does the right thing. The important
> point from all callers' perspective is that the combination of pointers
> is consistent for this rcu_read_lock. And rcu_dereference enforces the
> callers do hold rcu_read_lock.
>
> I didn't check all the conversions, just stared at the heart of the
> problem.
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

Thanks.

Going to fix that up,
Christian.

> -Chris

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-08-07  9:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 15:01 [PATCH 1/8] dma-buf: fix busy wait for new shared fences Christian König
2019-08-06 15:01 ` [PATCH 2/8] dma-buf: fix shared fence list handling in reservation_object_copy_fences Christian König
2019-08-06 19:06   ` Chris Wilson
2019-08-07 10:43     ` Christian König
2019-08-06 15:01 ` [PATCH 3/8] drm/i915: stop using seqcount for fenc pruning Christian König
2019-08-06 19:07   ` Chris Wilson
2019-08-06 15:01 ` [PATCH 4/8] drm/i915: use new reservation_object_fences helper Christian König
2019-08-06 19:09   ` Chris Wilson
2019-08-06 15:01 ` [PATCH 5/8] dma-buf: further relax reservation_object_add_shared_fence Christian König
2019-08-06 19:25   ` Chris Wilson
2019-08-06 15:01 ` [PATCH 6/8] dma-buf: simplify reservation_object_get_fences_rcu a bit Christian König
2019-08-06 19:11   ` Chris Wilson
2019-08-06 15:01 ` [PATCH 7/8] dma-buf: add reservation_object_fences helper Christian König
2019-08-06 19:24   ` Chris Wilson
2019-08-07  9:06     ` Christian König [this message]
2019-08-06 15:01 ` [PATCH 8/8] dma-buf: nuke reservation_object seq number Christian König
2019-08-06 19:57   ` Chris Wilson
2019-08-07 12:08     ` Christian König
2019-08-07 12:19       ` Chris Wilson
2019-08-07 13:05         ` Koenig, Christian
2019-08-06 18:57 ` [PATCH 1/8] dma-buf: fix busy wait for new shared fences Chris Wilson
2019-08-09 13:27 ` ✗ Fi.CI.BAT: failure for series starting with [1/8] " Patchwork

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=7dfbf200-2cee-ac38-0063-fded38d7809e@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=intel-gfx@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    /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