Are you sure? It seems like WDDM has a user-mode "User-mode display driver" - which looks to me like the HW-specific part of Mesa: it's invoked by the D3D runtime - and a "Display miniport driver", which is in the kernel.
That said, no doubt Linux's ability to reset drivers is way, way behind... We're coming up on 20 years since Windows could recover from a graphics driver reset reliably without losing the desktop, and only partial hacks exist on Linux today.
I really need to get around to building a sample HTML page to show how unsafe having WebGL enabled on Linux browsers is. One long shader, and your desktop is a goner.
Are you sure?
I'm not a Windows system architect but I see the Radeon driver on my iGPU under Windows crash all the time in reproducible scenarios.
The only time the system can recover is when the display compositor crashes (Wayland)
Are you sure? It seems like WDDM has a user-mode "User-mode display driver" - which looks to me like the HW-specific part of Mesa: it's invoked by the D3D runtime - and a "Display miniport driver", which is in the kernel.
See https://learn.microsoft.com/en-us/windows-hardware/drivers/display/windows-vista-and-later-display-driver-model-operation-flow
That said, no doubt Linux's ability to reset drivers is way, way behind... We're coming up on 20 years since Windows could recover from a graphics driver reset reliably without losing the desktop, and only partial hacks exist on Linux today.
I really need to get around to building a sample HTML page to show how unsafe having WebGL enabled on Linux browsers is. One long shader, and your desktop is a goner.
I'm not a Windows system architect but I see the Radeon driver on my iGPU under Windows crash all the time in reproducible scenarios.
The only time the system can recover is when the display compositor crashes (Wayland)