From: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>
To: "Brost, Matthew" <matthew.brost@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: Christian König <christian.koenig@amd.com>,
"Cavitt, Jonathan" <jonathan.cavitt@intel.com>
Subject: RE: [PATCH] drm/i915/selftests: Fix build after dma-fence locking rework
Date: Mon, 23 Feb 2026 19:01:57 +0000 [thread overview]
Message-ID: <CH0PR11MB544439AE2C3E9141EED7E7B0E577A@CH0PR11MB5444.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20260223172553.1663749-1-matthew.brost@intel.com>
-----Original Message-----
From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Matthew Brost
Sent: Monday, February 23, 2026 9:26 AM
To: intel-xe@lists.freedesktop.org; dri-devel@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
Cc: Christian König <christian.koenig@amd.com>
Subject: [PATCH] drm/i915/selftests: Fix build after dma-fence locking rework
>
> The i915_active selftest no longer builds after the dma-fence locking
> rework because it directly accessed the fence’s spinlock. The helper
> dma_fence_spinlock() must now be used to obtain the spinlock. Update the
> selftest to use dma_fence_spinlock() accordingly.
>
> Fixes: 1f32f310a13c ("dma-buf: inline spinlock for fence protection v5")
> Cc: Christian König <christian.koenig@amd.com>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
-Jonathan Cavitt
> ---
> drivers/gpu/drm/i915/selftests/i915_active.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/selftests/i915_active.c b/drivers/gpu/drm/i915/selftests/i915_active.c
> index 52345073b409..9fea2fabeac4 100644
> --- a/drivers/gpu/drm/i915/selftests/i915_active.c
> +++ b/drivers/gpu/drm/i915/selftests/i915_active.c
> @@ -323,9 +323,9 @@ static void active_flush(struct i915_active *ref,
> if (!fence)
> return;
>
> - spin_lock_irq(fence->lock);
> + spin_lock_irq(dma_fence_spinlock(fence));
> __list_del_entry(&active->cb.node);
> - spin_unlock_irq(fence->lock); /* serialise with fence->cb_list */
> + spin_unlock_irq(dma_fence_spinlock(fence)); /* serialise with fence->cb_list */
> atomic_dec(&ref->count);
>
> GEM_BUG_ON(!test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence->flags));
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2026-02-23 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 17:25 [PATCH] drm/i915/selftests: Fix build after dma-fence locking rework Matthew Brost
2026-02-23 19:01 ` Cavitt, Jonathan [this message]
2026-02-23 19:13 ` Christian König
2026-02-23 19:20 ` Matthew Brost
2026-02-23 19:33 ` Christian König
2026-02-23 19:36 ` Matthew Brost
2026-02-23 20:03 ` Christian König
2026-02-23 23:54 ` Claude review: " Claude Code Review Bot
2026-02-23 23:54 ` Claude Code Review Bot
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=CH0PR11MB544439AE2C3E9141EED7E7B0E577A@CH0PR11MB5444.namprd11.prod.outlook.com \
--to=jonathan.cavitt@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.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