drm/scheduler: move last_sched fence updating prior to job popping (v2)
authorPixel Ding <Pixel.Ding@amd.com>
Wed, 18 Apr 2018 08:37:40 +0000 (04:37 -0400)
committerAlex Deucher <alexander.deucher@amd.com>
Tue, 15 May 2018 18:43:30 +0000 (13:43 -0500)
commitb5b4ea4d98b42f94442e5d46d5942f392ed8af56
tree6c0b82e8aaf998a17d9925e11112dcd30d560873
parenta4b3996aeebbaafd2682f4db06bb5659e1653da7
drm/scheduler: move last_sched fence updating prior to job popping (v2)

Make sure main thread won't update last_sched fence when entity
is cleanup.

Fix a racing issue which is caused by putting last_sched fence
twice. Running vulkaninfo in tight loop can produce this issue
as seeing wild fence pointer.

v2: squash in build fix (Christian)

Signed-off-by: Pixel Ding <Pixel.Ding@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Monk Liu <Monk.Liu@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drivers/gpu/drm/scheduler/gpu_scheduler.c