drm/amdkfd: Fix TCP XNACK scoreboard reset race on MI300

Browse source

Fix a hardware RTL bug in the TCP XNACK scoreboard reset path on MI300,
where a wave receiving a no-retry FAULT from UTC and subsequently
terminating may leave its scoreboard entry uncleared when reset events
arrive back-to-back.

This can cause a later, unrelated wave using the same scoreboard slot
to incorrectly inherit the XNACK error state, resulting in its VMEM
operations being dropped even though the wave never faulted.

Signed-off-by: Gang Ba <Gang.Ba@amd.com>
Reviewed-by: Jay Cornwall <jay.cornwall@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

...

This commit is contained in:

Gang Ba 2026-09-21 13:37:13 -04:00 • committed by Alex Deucher

parent 24c946017b

commit 923d09ab1f

5 changed files with 17 additions and 13 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

3

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

View file

2

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

View file

11

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

View file

2

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

View file

12

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

View file