drm/amdgpu: Prefer RAS recovery for scheduler hang

Browse source

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 <lijo.lazar@amd.com>
Reviewed-by: Hawking Zhang <Hawking.Zhang@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

...

This commit is contained in:

Lijo Lazar 2024-10-24 11:01:57 +05:30 • committed by Alex Deucher

parent 0eecff79e4

commit e1ee2111ca

5 changed files with 78 additions and 7 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

drivers/gpu/drm/amd/amdgpu/aldebaran.c

View file

15

drivers/gpu/drm/amd/amdgpu/amdgpu_device.c

View file

55

drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c

View file

11

drivers/gpu/drm/amd/amdgpu/amdgpu_ras.h

View file

2

drivers/gpu/drm/amd/amdkfd/kfd_int_process_v9.c

View file