Answers are grounded in this paper and cite their sources.
This record presents an independent causal validation of AMD ROCm GPU access under Windows Subsystem for Linux containers in the context of Microsoft WSL issue #40988. Physical testing was performed on AMD Strix Halo (gfx1151) hardware using a WSL-aware ROCm userspace and a real HIP compute probe. Two controlled A/B experiments were performed. First, WSLC GPU projection using --gpus all with matched WSL-aware ROCm userspace produced successful HIP execution in 3/3 runs, while the corresponding control without GPU projection failed HIP initialisation in 3/3 runs. Second, with /dev/dxg present, enabling the DXG backend produced successful execution in 3/3 runs, while disabling DXG backend detection produced failure in 3/3 runs. The evidence supports the conclusion that the validated WSL GPU path is /dev/dxg together with ROCDXG/HSA/HIP userspace, rather than native Linux /dev/kfd passthrough. No Microsoft source patch was required by the tested configuration. The record contains the technical white paper, editable DOCX source, and a reproducibility package containing raw evidence, probe source and binary, governed evaluation outputs, hashes, provenance information and reproduction instructions. Scope is limited to the tested Strix Halo gfx1151 environment and does not claim universal compatibility with all AMD GPUs or application workloads.
No takes yet. Share an insight, caveat, or question.
Nigel Hutchinson (2026) studied this question.
Synapse has enriched 8 closely related papers on similar clinical questions. Consider them for comparative context: