From: Arvind Yadav <Arvind.Yadav@amd.com>
To: <Christian.Koenig@amd.com>, <andrey.grodzovsky@amd.com>,
<shashank.sharma@amd.com>, <amaranath.somalapuram@amd.com>,
<Arunpravin.PaneerSelvam@amd.com>, <sumit.semwal@linaro.org>,
<gustavo@padovan.org>, <airlied@linux.ie>, <daniel@ffwll.ch>,
<linux-media@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<linaro-mm-sig@lists.linaro.org>, <linux-kernel@vger.kernel.org>
Cc: Arvind Yadav <Arvind.Yadav@amd.com>
Subject: [PATCH 0/3] dma-buf: Check status of enable-signaling bit on debug
Date: Tue, 27 Sep 2022 22:54:06 +0530 [thread overview]
Message-ID: <20220927172409.484061-1-Arvind.Yadav@amd.com> (raw)
Fence signaling must be enabled to make sure that
the dma_fence_is_signaled() and dma_fence_is_signaled_locked()
function ever returns true. Since drivers and implementations
sometimes mess this up, this ensures correct behaviour when
DEBUG_WW_MUTEX_SLOWPATH is used during debugging.
This should make any implementation bugs resulting in not
signaled fences much more obvious.
Arvind Yadav (3):
[PATCH 1/3] dma-buf: Remove the signaled bit status check
[PATCH 2/3] dma-buf: Enable signaling on fence for sw_sync
[PATCH 3/3] dma-buf: Check status of enable-signaling bit on debug
drivers/dma-buf/dma-fence.c | 5 -----
drivers/dma-buf/sw_sync.c | 2 ++
include/linux/dma-fence.h | 5 +++++
3 files changed, 7 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2022-09-27 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 17:24 Arvind Yadav [this message]
2022-09-27 17:24 ` [PATCH 1/3] dma-buf: Remove the signaled bit status check Arvind Yadav
2022-09-29 18:14 ` Christian König
2022-09-27 17:24 ` [PATCH 2/3] dma-buf: Enable signaling on fence for sw_sync Arvind Yadav
2022-09-29 18:17 ` Christian König
2022-09-27 17:24 ` [PATCH 3/3] dma-buf: Check status of enable-signaling bit on debug Arvind Yadav
2022-09-29 18:18 ` Christian König
2022-09-29 18:30 ` Yadav, Arvind
2022-09-29 18:32 ` Christian König
2022-09-30 7:32 ` Yadav, Arvind
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=20220927172409.484061-1-Arvind.Yadav@amd.com \
--to=arvind.yadav@amd.com \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=airlied@linux.ie \
--cc=amaranath.somalapuram@amd.com \
--cc=andrey.grodzovsky@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=shashank.sharma@amd.com \
--cc=sumit.semwal@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
all inboxes | Powered by JetHome®