On 2016å¹´08æ??17æ?¥ 20:26, Christian König wrote:
> From: Christian König <christian.koenig at amd.com>
>
> Could be that we don't actually have a timeout set.
>
> Signed-off-by: Christian König <christian.koenig at amd.com>
Reviewed-by: Chunming Zhou <david1.zhou at amd.com>
> ---
> drivers/gpu/drm/amd/scheduler/gpu_scheduler.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c b/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c
> index f96aa82..f3fc10f 100644
> --- a/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c
> +++ b/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c
> @@ -407,7 +407,7 @@ void amd_sched_job_recovery(struct amd_gpu_scheduler *sched)
> spin_lock(&sched->job_list_lock);
> s_job = list_first_entry_or_null(&sched->ring_mirror_list,
> struct amd_sched_job, node);
> - if (s_job)
> + if (s_job && sched->timeout != MAX_SCHEDULE_TIMEOUT)
> schedule_delayed_work(&s_job->work_tdr, sched->timeout);
>
> list_for_each_entry_safe(s_job, tmp, &sched->ring_mirror_list, node) {
