summaryrefslogtreecommitdiff
path: root/tools/lib/python/kdoc/python_version.py
diff options
context:
space:
mode:
authorTimur Kristóf <timur.kristof@gmail.com>2026-10-07 00:02:52 +0200
committerAlex Deucher <alexander.deucher@amd.com>2026-10-15 12:46:58 -0400
commit752480ad62964edf0254e151110d3e53a7cb37de (patch)
tree6558326d264888a67e83e855502259d05aef3f78 /tools/lib/python/kdoc/python_version.py
parent3c44cbcec5eb370713bbd2c315ed7c34d8ccec2b (diff)
downloadlinux-next-752480ad62964edf0254e151110d3e53a7cb37de.tar.gz
linux-next-752480ad62964edf0254e151110d3e53a7cb37de.zip
drm/amdgpu/sdma3: Work around POLL_REGMEM / FENCE hang
SDMA can randomly hang on Polaris 10. Hard to reproduce, but has been occurring sporadically in the Mesa CI on the RADV Polaris 10 job even when Mesa isn't using the SDMA engine. When Mesa actually uses the SDMA on Polaris, the hang becomes more frequent and the reproduction rate goes up significantly in the CI system. We don't know why the hangs occur, but it seems that inserting a single NOP packet before each POLL_REGMEM and FENCE packet works around it. At the moment it's unclear which GPUs are affected, so let's apply this to SDMA 3.x for now. Note that this issue is not documented or acknowledged by AMD. Reviewed-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Timur Kristóf <timur.kristof@gmail.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> (cherry picked from commit c343a27ed90823d08de125f7c447d96d056b75d9) Cc: stable@vger.kernel.org
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions