# Proposed AMD GPU kernel patches target sparse-binding stutter in Proton games

A 10-patch amdgpu series posted on November 17 batches and explicitly syncs sparse memory mapping to cut stutter. It is a proposal, not in mainline Linux.

- By Elvis, published 2026-11-19T17:11:00Z
- Topics: Software
- Handhelds: Valve Steam Deck OLED, Valve Steam Deck LCD
- Web page: https://handheldquest.com/news/amdgpu-kernel-patches-sparse-binding-stutter-proton/

Natalie Vock posted a 10-patch series for amdgpu, the Linux kernel's driver for AMD Radeon graphics, to the amd-gfx mailing list on November 17. Its goal is to stop heavy sparse-binding work from stalling a game's rendering, which shows up as hitches in some Windows games running through Proton. Steam Deck HQ, which reported it on November 18, describes Vock as a contractor on Valve's Linux graphics driver team. As of November 19 the series is a proposal on the mailing list, not part of the mainline kernel. Valve's SteamOS 3.10.1 Preview notes of November 17 don't mention it.

Specs: [Valve Steam Deck OLED](https://handheldquest.com/handhelds/steam-deck-oled/)

## What the patches change

The hitch Vock describes has two parts. On the GPU, a frame's graphics and compute work ends up waiting on memory-mapping updates for sparse resources (PRT mappings, in the cover letter), because the driver ties those updates to everything else in flight. The SDMA copy engine is supposed to handle that mapping work in parallel, and the games that hit this are the ones that move a lot of sparse memory around while they render. On the CPU, every mapping change is its own ioctl (a call into the kernel), so the cost grows with the number of changes.

For the GPU side, the first patches let the driver know exactly which mappings a given update removed, so it can synchronise just those unmaps instead of everything. For the CPU side, changes can be queued, validated as a group and committed together, with a rollback path if one fails. Patch 9 exposes this through a new ioctl, AMDGPU_GEM_VA2: one call carries many mapping operations, and it can wait on and signal several sync objects, timeline sync objects included.

The new call is deliberately not a drop-in change. Vock lists explicit synchronisation as a breaking difference from the existing AMDGPU_GEM_VA call: earlier submissions are not necessarily waited on. That is why it is a separate ioctl. Patch 9 says games that issue lots of sparse operations, some Proton titles in particular, should see significant stutter reductions when they use it. No frame-time figures are posted with the series.

## How far it is from a Deck

Version 1, three patches titled "Explicit sync for PRT unmaps", went to the list on May 29. Version 2 grows to 10 patches and adds the batching. It touches 15 files, with 1,099 lines added and 311 removed. In a reply on the thread on November 17 (UTC), Dave Airlie asked whether the ioctl could be named VM_BIND to match the Intel xe and nouveau drivers.

The kernel docs say amdgpu covers every Radeon GPU built on GCN, RDNA or CDNA, which includes the RDNA 2 graphics in the [Steam Deck OLED](https://handheldquest.com/handhelds/steam-deck-oled/) and [LCD model](https://handheldquest.com/handhelds/steam-deck-lcd/). Steam Deck HQ says the patch will directly affect Deck games, but it isn't sure when: the kernel has to accept it first, then SteamOS has to move to a kernel version that includes it. It also expects gains only in games that use sparse binding this way, not an improvement across the board. Our reading of patch 9 adds one more step: because the gain comes through the new ioctl, the Vulkan driver that Proton games run on also has to call it. The posting doesn't name a matching driver change or give any timeline. The [SteamOS 3.10 Preview](https://handheldquest.com/news/steamos-3-10-preview-linux-7-3-plasma-6-8-hdmi-vrr/) of November 14 is based on Linux 7.3, and its 3.10.1 update lists no change of this kind, so Deck owners on the Preview channel don't have it either.

## Sources

1. Linux kernel mailing list (amd-gfx), "[PATCH v2 00/10] drm/amdgpu: Rework VM update ops for batching and explicit sync": https://lore.kernel.org/amd-gfx/20261117-prt-explicit-sync-v2-0-bb3851cb6a0c@pixelcluster.dev/
2. Linux kernel mailing list (amd-gfx), "[PATCH v2 09/10] drm/amdgpu: Add new AMDGPU_GEM_VA2 ioctl": https://lore.kernel.org/amd-gfx/20261117-prt-explicit-sync-v2-9-bb3851cb6a0c@pixelcluster.dev/
3. Linux kernel mailing list (amd-gfx), "Re: [PATCH v2 09/10] drm/amdgpu: Add new AMDGPU_GEM_VA2 ioctl (Dave Airlie)": https://lore.kernel.org/amd-gfx/CAPM=9tzeLEgavoAwjp2H0Y55STxRr6P8_LHHM5YWLkr9qJ2Lwg@mail.gmail.com/
4. Linux kernel mailing list (amd-gfx), "[PATCH 0/3] drm/amdgpu: Explicit sync for PRT unmaps": https://lore.kernel.org/amd-gfx/20260529-prt-explicit-sync-v1-0-9f1c60955cab@gmx.de/
5. The Linux Kernel documentation, "drm/amdgpu AMDgpu driver": https://docs.kernel.org/gpu/amdgpu/index.html
6. Valve, "SteamOS 3.10.1 Preview": https://steamcommunity.com/games/1675200/announcements/detail/687522235410285839
7. Steam Deck HQ, "New Linux GPU Patch Could Significantly Reduce Stuttering On Steam Deck": https://steamdeckhq.com/news/linux-kernel-patch-targets-stuttering/
