Re:GPU profiling for WebGPU workloads on Windows with Chrome
by _factor on Saturday July 06, 2024 @08:13AM
(#40889943)
“WebGPU is supposed to be properly sandboxed.“
GPU must therefore provide open API for proprietary processing space.
Magic “packets” are therefore possible to execute arbitrary functions on “sandboxed” DMA devices.
Still a problem until we can audit the hardware. NV, and to a lesser extent AMD and ARC play somewhat open with a few omnipotent cards in their pockets. The prime of the issue is that gamers don’t care, only security professionals do. Because they’re the ones who see the 0-days fly by every day.
GPU must therefore provide open API for proprietary processing space.
Magic “packets” are therefore possible to execute arbitrary functions on “sandboxed” DMA devices.
Still a problem until we can audit the hardware. NV, and to a lesser extent AMD and ARC play somewhat open with a few omnipotent cards in their pockets. The prime of the issue is that gamers don’t care, only security professionals do. Because they’re the ones who see the 0-days fly by every day.