[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220905163502.4032-1-Arvind.Yadav@amd.com>
Date: Mon, 5 Sep 2022 22:04:58 +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 v2 0/4] dma-buf: To check enable signaling before signaled
TTM, GEM, DRM or the core DMA-buf framework are needs
to enable software signaling before the fence is signaled.
The core DMA-buf framework software can forget to call
enable_signaling before the fence is signaled. It means
framework code can forget to call dma_fence_enable_sw_signaling()
before calling dma_fence_is_signaled(). To avoid this scenario
on debug kernel, check the DMA_FENCE_FLAG_ENABLE_SIGNAL_BIT bit
status before checking the MA_FENCE_FLAG_SIGNALED_BIT bit status
to confirm that software signaling is enabled.
Arvind Yadav (4):
[PATCH v2 1/4] drm/sched: Enable signaling for finished fence
[PATCH v2 2/4] dma-buf: enable signaling for the stub fence on debug
[PATCH v2 3/4] dma-buf: enable signaling for selftest fence on debug
[PATCH v2 4/4] dma-buf: Check status of enable-signaling bit on debug
drivers/dma-buf/dma-fence.c | 7 ++++
drivers/dma-buf/st-dma-fence-chain.c | 8 +++++
drivers/dma-buf/st-dma-fence-unwrap.c | 44 ++++++++++++++++++++++++++
drivers/dma-buf/st-dma-fence.c | 25 ++++++++++++++-
drivers/dma-buf/st-dma-resv.c | 20 ++++++++++++
drivers/gpu/drm/scheduler/sched_main.c | 2 ++
include/linux/dma-fence.h | 5 +++
7 files changed, 110 insertions(+), 1 deletion(-)
--
2.25.1
Powered by blists - more mailing lists