From: "Yadav, Arvind" <arvyadav@amd.com>
To: "Christian König" <christian.koenig@amd.com>,
"Arvind Yadav" <Arvind.Yadav@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
Subject: Re: [PATCH v4 0/6] dma-buf: Check status of enable-signaling bit on debug
Date: Thu, 15 Sep 2022 18:32:16 +0530 [thread overview]
Message-ID: <33a16b15-3d3c-7485-d021-ee2a727e5391@amd.com> (raw)
In-Reply-To: <d2d81ffd-2269-bdc6-0daa-8f3a99306e46@amd.com>
On 9/15/2022 5:37 PM, Christian König wrote:
> Is that sufficient to allow running a desktop on amdgpu with the extra
> check enabled? If yes that would be quite a milestone.
>
Yes, It is running on amdgpu with extra config enabled.
> What's left is checking the userspace IGT tests. Especially the
> sync_file and drm_syncobj tests I would expect to have problems with
> this extra check.
>
Yes, IGT test cases are failing .
~Arvind
> Thanks,
> Christian.
>
> Am 14.09.22 um 18:43 schrieb Arvind Yadav:
>> Fence signaling must be enabled to make sure that
>> the dma_fence_is_signaled() 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 (6):
>> [PATCH v4 1/6] dma-buf: Remove the signaled bit status check
>> [PATCH v4 2/6] dma-buf: set signaling bit for the stub fence
>> [PATCH v4 3/6] dma-buf: Enable signaling on fence for selftests
>> [PATCH v4 4/6] dma-buf: dma_fence_wait must enable signaling
>> [PATCH v4 5/6] drm/sched: Use parent fence instead of finished
>> [PATCH v4 6/6] dma-buf: Check status of enable-signaling bit on debug
>>
>> drivers/dma-buf/Kconfig | 7 +++++++
>> drivers/dma-buf/dma-fence.c | 16 ++++++++++------
>> drivers/dma-buf/st-dma-fence-chain.c | 4 ++++
>> drivers/dma-buf/st-dma-fence-unwrap.c | 22 ++++++++++++++++++++++
>> drivers/dma-buf/st-dma-fence.c | 16 ++++++++++++++++
>> drivers/dma-buf/st-dma-resv.c | 10 ++++++++++
>> drivers/gpu/drm/scheduler/sched_main.c | 4 ++--
>> include/linux/dma-fence.h | 5 +++++
>> 8 files changed, 76 insertions(+), 8 deletions(-)
>>
>
next prev parent reply other threads:[~2022-09-15 13:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 16:43 Arvind Yadav
2022-09-14 16:43 ` [PATCH v4 1/6] dma-buf: Remove the signaled bit status check Arvind Yadav
2022-09-14 16:43 ` [PATCH v4 2/6] dma-buf: set signaling bit for the stub fence Arvind Yadav
2022-09-14 16:43 ` [PATCH v4 3/6] dma-buf: Enable signaling on fence for selftests Arvind Yadav
2022-09-14 16:43 ` [PATCH v4 4/6] dma-buf: dma_fence_wait must enable signaling Arvind Yadav
2022-09-15 12:06 ` Christian König
2022-09-14 16:43 ` [PATCH v4 5/6] drm/sched: Use parent fence instead of finished Arvind Yadav
2022-09-29 14:53 ` Steven Price
2022-09-29 14:57 ` Christian König
2022-09-29 15:31 ` Steven Price
2022-09-29 17:07 ` [Linaro-mm-sig] " Christian König
2022-09-14 16:43 ` [PATCH v4 6/6] dma-buf: Check status of enable-signaling bit on debug Arvind Yadav
2022-09-15 12:06 ` Christian König
2022-09-15 12:07 ` [PATCH v4 0/6] " Christian König
2022-09-15 13:02 ` Yadav, Arvind [this message]
2022-09-15 16:05 ` Christian König
2022-09-17 6:17 ` Ville Syrjälä
2022-09-17 15:18 ` [Linaro-mm-sig] " Christian König
2022-09-19 11:26 ` Ville Syrjälä
2022-09-19 11:38 ` 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=33a16b15-3d3c-7485-d021-ee2a727e5391@amd.com \
--to=arvyadav@amd.com \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=Arvind.Yadav@amd.com \
--cc=airlied@linux.ie \
--cc=amaranath.somalapuram@amd.com \
--cc=andrey.grodzovsky@amd.com \
--cc=christian.koenig@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®