Am 24.10.2017 um 10:42 schrieb Monk Liu:
because no hw fence may also comes from a gpu recover
and job skip event, doesn't mean really bad thing
Change-Id: I4d6e5824dfe050bb3ca6ea0ad74828720bc374ac
Signed-off-by: Monk Liu <[email protected]>
Reviewed-by: Christian König <[email protected]>
---
drivers/gpu/drm/amd/scheduler/gpu_scheduler.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c
b/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c
index 9cbeade..10d49b1 100644
--- a/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c
+++ b/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c
@@ -525,7 +525,6 @@ void amd_sched_job_recovery(struct amd_gpu_scheduler *sched)
r);
dma_fence_put(fence);
} else {
- DRM_ERROR("Failed to run job!\n");
amd_sched_process_job(NULL, &s_fence->cb);
}
spin_lock(&sched->job_list_lock);
@@ -664,7 +663,6 @@ static int amd_sched_main(void *param)
r);
dma_fence_put(fence);
} else {
- DRM_ERROR("Failed to run job!\n");
amd_sched_process_job(NULL, &s_fence->cb);
}
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
