diff options
author | Andrey Grodzovsky <andrey.grodzovsky@amd.com> | 2018-10-18 12:32:46 -0400 |
---|---|---|
committer | Alex Deucher <alexander.deucher@amd.com> | 2018-11-05 14:21:22 -0500 |
commit | faf6e1a87e07423a729e04fb2e8188742e89ea4c (patch) | |
tree | 51c205851d3e99371bbf271b8f7e3e59b32ceb04 /drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | |
parent | 2bb42410b1bd324912389c6ac748df1c1befd69f (diff) | |
download | linux-stable-faf6e1a87e07423a729e04fb2e8188742e89ea4c.tar.gz linux-stable-faf6e1a87e07423a729e04fb2e8188742e89ea4c.tar.bz2 linux-stable-faf6e1a87e07423a729e04fb2e8188742e89ea4c.zip |
drm/sched: Add boolean to mark if sched is ready to work v5
Problem:
A particular scheduler may become unsuable (underlying HW) after
some event (e.g. GPU reset). If it's later chosen by
the get free sched. policy a command will fail to be
submitted.
Fix:
Add a driver specific callback to report the sched status so
rq with bad sched can be avoided in favor of working one or
none in which case job init will fail.
v2: Switch from driver callback to flag in scheduler.
v3: rebase
v4: Remove ready paramter from drm_sched_init, set
uncoditionally to true once init done.
v5: fix missed change in v3d in v4 (Alex)
Signed-off-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c')
0 files changed, 0 insertions, 0 deletions