[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220927172409.484061-4-Arvind.Yadav@amd.com>
Date: Tue, 27 Sep 2022 22:54:09 +0530
From: Arvind Yadav <Arvind.Yadav@....com>
To: <Christian.Koenig@....com>, <andrey.grodzovsky@....com>,
<shashank.sharma@....com>, <amaranath.somalapuram@....com>,
<Arunpravin.PaneerSelvam@....com>, <sumit.semwal@...aro.org>,
<gustavo@...ovan.org>, <airlied@...ux.ie>, <daniel@...ll.ch>,
<linux-media@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
<linaro-mm-sig@...ts.linaro.org>, <linux-kernel@...r.kernel.org>
CC: Arvind Yadav <Arvind.Yadav@....com>
Subject: [PATCH 3/3] dma-buf: Check status of enable-signaling bit on debug
Fence signaling must be enabled to make sure that
the dma_fence_is_signaled_locked() function ever returns true.
Since drivers and implementations sometimes mess this up,
this ensures correct behaviour when DMABUF_DEBUG_ENABLE_SIGNALING
is used during debugging.
This should make any implementation bugs resulting in not
signaled fences much more obvious.
Signed-off-by: Arvind Yadav <Arvind.Yadav@....com>
---
include/linux/dma-fence.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/linux/dma-fence.h b/include/linux/dma-fence.h
index 775cdc0b4f24..5156dc6be0a6 100644
--- a/include/linux/dma-fence.h
+++ b/include/linux/dma-fence.h
@@ -398,6 +398,11 @@ void dma_fence_enable_sw_signaling(struct dma_fence *fence);
static inline bool
dma_fence_is_signaled_locked(struct dma_fence *fence)
{
+#ifdef CONFIG_DMABUF_DEBUG_ENABLE_SIGNALING
+ if (!test_bit(DMA_FENCE_FLAG_ENABLE_SIGNAL_BIT, &fence->flags))
+ return false;
+#endif
+
if (test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence->flags))
return true;
--
2.25.1
Powered by blists - more mailing lists