From: Philipp Stanner <phasta@mailbox.org>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
tursulin@ursulin.net, matthew.brost@intel.com,
sumit.semwal@linaro.org
Cc: dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH 7/9] dma-buf: use inline lock for the stub fence v2
Date: Wed, 21 Jan 2026 10:29:19 +0100 [thread overview]
Message-ID: <697fb47b7c1bad47a413fb7c60778f78263be4df.camel@mailbox.org> (raw)
In-Reply-To: <20260120105655.7134-8-christian.koenig@amd.com>
On Tue, 2026-01-20 at 11:54 +0100, Christian König wrote:
> Using the inline lock is now the recommended way for dma_fence
> implementations.
>
> So use this approach for the framework's internal fences as well.
>
> Also saves about 4 bytes for the external spinlock.
>
> v2: drop unnecessary changes
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Reviewed-by: Philipp Stanner <phasta@kernel.org>
> ---
> drivers/dma-buf/dma-fence.c | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/dma-buf/dma-fence.c b/drivers/dma-buf/dma-fence.c
> index 36ff0e5098ee..03a09acdeaec 100644
> --- a/drivers/dma-buf/dma-fence.c
> +++ b/drivers/dma-buf/dma-fence.c
> @@ -24,7 +24,6 @@ EXPORT_TRACEPOINT_SYMBOL(dma_fence_emit);
> EXPORT_TRACEPOINT_SYMBOL(dma_fence_enable_signal);
> EXPORT_TRACEPOINT_SYMBOL(dma_fence_signaled);
>
> -static DEFINE_SPINLOCK(dma_fence_stub_lock);
> static struct dma_fence dma_fence_stub;
>
> /*
> @@ -123,12 +122,9 @@ static const struct dma_fence_ops dma_fence_stub_ops = {
>
> static int __init dma_fence_init_stub(void)
> {
> - dma_fence_init(&dma_fence_stub, &dma_fence_stub_ops,
> - &dma_fence_stub_lock, 0, 0);
> -
> + dma_fence_init(&dma_fence_stub, &dma_fence_stub_ops, NULL, 0, 0);
> set_bit(DMA_FENCE_FLAG_ENABLE_SIGNAL_BIT,
> &dma_fence_stub.flags);
> -
> dma_fence_signal(&dma_fence_stub);
> return 0;
> }
> @@ -160,11 +156,7 @@ struct dma_fence *dma_fence_allocate_private_stub(ktime_t timestamp)
> if (fence == NULL)
> return NULL;
>
> - dma_fence_init(fence,
> - &dma_fence_stub_ops,
> - &dma_fence_stub_lock,
> - 0, 0);
> -
> + dma_fence_init(fence, &dma_fence_stub_ops, NULL, 0, 0);
> set_bit(DMA_FENCE_FLAG_ENABLE_SIGNAL_BIT,
> &fence->flags);
>
next prev parent reply other threads:[~2026-01-21 9:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 10:54 Independence for dma_fences! v6 Christian König
2026-01-20 10:54 ` [PATCH 1/9] dma-buf: add dma_fence_was_initialized function v2 Christian König
2026-01-20 11:33 ` Tvrtko Ursulin
2026-07-13 8:58 ` Jiri Slaby
2026-07-14 7:53 ` Philipp Stanner
2026-07-14 8:43 ` Philipp Stanner
2026-08-19 8:59 ` Jiri Slaby
2026-08-19 12:33 ` Philipp Stanner
2026-08-19 12:51 ` Philipp Stanner
2026-08-28 7:29 ` Jiri Slaby
2026-08-28 7:46 ` Jiri Slaby
2026-08-28 8:32 ` Jiri Slaby
2026-09-02 6:52 ` Philipp Stanner
2026-09-02 6:56 ` Jiri Slaby
2026-09-02 7:03 ` Philipp Stanner
2026-09-02 10:47 ` Jiri Slaby
2026-01-20 10:54 ` [PATCH 2/9] dma-buf: protected fence ops by RCU v5 Christian König
2026-01-20 10:54 ` [PATCH 3/9] dma-buf: detach fence ops on signal v2 Christian König
2026-01-20 10:54 ` [PATCH 4/9] dma-buf: abstract fence locking Christian König
2026-01-20 10:54 ` [PATCH 5/9] dma-buf: inline spinlock for fence protection v4 Christian König
2026-01-20 11:41 ` Tvrtko Ursulin
2026-01-21 8:48 ` Christian König
2026-01-21 9:03 ` Tvrtko Ursulin
2026-01-27 4:56 ` kernel test robot
2026-01-20 10:54 ` [PATCH 6/9] dma-buf/selftests: test RCU ops and inline lock v2 Christian König
2026-01-20 10:54 ` [PATCH 7/9] dma-buf: use inline lock for the stub fence v2 Christian König
2026-01-21 9:29 ` Philipp Stanner [this message]
2026-01-20 10:54 ` [PATCH 8/9] dma-buf: use inline lock for the dma-fence-array Christian König
2026-01-20 10:54 ` [PATCH 9/9] dma-buf: use inline lock for the dma-fence-chain Christian König
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=697fb47b7c1bad47a413fb7c60778f78263be4df.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=matthew.brost@intel.com \
--cc=phasta@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tursulin@ursulin.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