aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_isp.c
diff options
context:
space:
mode:
authorLijo Lazar <[email protected]>2024-10-24 05:31:57 +0000
committerAlex Deucher <[email protected]>2024-12-10 15:26:46 +0000
commite1ee2111ca48169a9fdc5075f7863f5d4d591e2f (patch)
tree487517237aa6a8c5587ef88e717accf3a72878b2 /drivers/gpu/drm/amd/amdgpu/amdgpu_isp.c
parentdrm/amdgpu: do RAS MCA2PA conversion in device init phase (diff)
downloadkernel-e1ee2111ca48169a9fdc5075f7863f5d4d591e2f.tar.gz
kernel-e1ee2111ca48169a9fdc5075f7863f5d4d591e2f.zip
drm/amdgpu: Prefer RAS recovery for scheduler hang
Before scheduling a recovery due to scheduler/job hang, check if a RAS error is detected. If so, choose RAS recovery to handle the situation. A scheduler/job hang could be the side effect of a RAS error. In such cases, it is required to go through the RAS error recovery process. A RAS error recovery process in certains cases also could avoid a full device device reset. An error state is maintained in RAS context to detect the block affected. Fatal Error state uses unused block id. Set the block id when error is detected. If the interrupt handler detected a poison error, it's not required to look for a fatal error. Skip fatal error checking in such cases. Signed-off-by: Lijo Lazar <[email protected]> Reviewed-by: Hawking Zhang <[email protected]> Signed-off-by: Alex Deucher <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_isp.c')
0 files changed, 0 insertions, 0 deletions