From: Donggeun Yoo <donggeunyoo.kernel@gmail.com>
To: "Christian König" <christian.koenig@amd.com>, phasta@kernel.org
Cc: Donggeun Yoo <donggeunyoo.kernel@gmail.com>,
Philipp Stanner <phasta@mailbox.org>,
Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
Luben Tuikov <ltuikov89@gmail.com>,
Matthew Brost <matthew.brost@intel.com>,
Danilo Krummrich <dakr@kernel.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: drm/sched: run queues freed before the TDR that drm_sched_fini() waits for
Date: Sat, 12 Sep 2026 10:48:12 +0900 [thread overview]
Message-ID: <20260912014812.2115452-1-donggeunyoo.kernel@gmail.com> (raw)
In-Reply-To: <363aa83e-7c72-4592-a8ca-46f0ab56e4c5@amd.com>
On 9/10/26 15:58, Christian König wrote:
> That is a really good point, canceling the timeout handler should indeed
> happen before freeing the runqueues.
Posted, in a separate thread:
https://lore.kernel.org/dri-devel/20260910121601.805032-1-donggeunyoo.kernel@gmail.com/
> Oh, that is completely broken behavior of the KUnit test case. I suggest to
> fix that as well.
Agreed - it never signals the hardware fence, on purpose, only to find out
whether the sequence was reachable at all. A local probe, not something
meant for the tree.
Regards,
Donggeun
prev parent reply other threads:[~2026-09-12 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 5:46 Donggeun Yoo
2026-09-10 6:52 ` Philipp Stanner
2026-09-10 7:04 ` Philipp Stanner
2026-09-10 7:32 ` Christian König
2026-09-10 8:44 ` Donggeun Yoo
2026-09-10 8:51 ` Philipp Stanner
2026-09-10 9:50 ` Donggeun Yoo
2026-09-10 11:04 ` Philipp Stanner
2026-09-10 13:58 ` Christian König
2026-09-12 1:48 ` Donggeun Yoo [this message]
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=20260912014812.2115452-1-donggeunyoo.kernel@gmail.com \
--to=donggeunyoo.kernel@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltuikov89@gmail.com \
--cc=matthew.brost@intel.com \
--cc=phasta@kernel.org \
--cc=phasta@mailbox.org \
--cc=tvrtko.ursulin@igalia.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
all inboxes | Powered by JetHome®