drm/nouveau: fence: fail to emit when fence context is killed
authorDanilo Krummrich <dakr@redhat.com>
Fri, 4 Aug 2023 18:23:48 +0000 (20:23 +0200)
committerDanilo Krummrich <dakr@redhat.com>
Fri, 4 Aug 2023 18:34:37 +0000 (20:34 +0200)
commitf124eef76f855d9f3df8827cb1e166f96994042c
treeb20774843f812b756f9e57a2598a35127fa6f55f
parent7f2a0b50b2b20308a19602b51c647566c62e144c
drm/nouveau: fence: fail to emit when fence context is killed

The new VM_BIND UAPI implementation introduced in subsequent commits
will allow asynchronous jobs processing push buffers and emitting
fences.

If a fence context is killed, e.g. due to a channel fault, jobs which
are already queued for execution might still emit new fences. In such a
case a job would hang forever.

To fix that, fail to emit a new fence on a killed fence context with
-ENODEV to unblock the job.

Reviewed-by: Dave Airlie <airlied@redhat.com>
Signed-off-by: Danilo Krummrich <dakr@redhat.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230804182406.5222-9-dakr@redhat.com
drivers/gpu/drm/nouveau/nouveau_fence.c
drivers/gpu/drm/nouveau/nouveau_fence.h