diff options
| author | Christian König <ckoenig.leichtzumerken@gmail.com> | 2025-03-12 14:44:00 +0100 |
|---|---|---|
| committer | Philipp Stanner <phasta@kernel.org> | 2025-03-12 15:02:12 +0100 |
| commit | c67c0fef5d4d1b888275a588f0fb0f6f2755924b (patch) | |
| tree | e8b1c2e2c2984159c48d2ac703af9e0156afbbb8 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | eff0347e7c228335e9ff64aaf02c66957803af6a (diff) | |
| download | kernel-c67c0fef5d4d1b888275a588f0fb0f6f2755924b.tar.gz | |
drm/sched: revert "drm_sched_job_cleanup(): correct false doc"
This reverts commit 44d2f310f008613c1dbe5e234c2cf2be90cbbfab.
The function drm_sched_job_arm() is indeed the point of no return. The
background is that it is nearly impossible for the driver to correctly
retract the fence and signal it in the order enforced by the dma_fence
framework.
The code in drm_sched_job_cleanup() is for the purpose to cleanup after
the job was armed through drm_sched_job_arm() *and* processed by the
scheduler.
We can certainly improve the documentation, but removing the warning is
clearly not a good idea.
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Philipp Stanner <phasta@kernel.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20250312134400.2176393-1-christian.koenig@amd.com
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions