On Mon, May 11, 2020 at 11:19:30AM +0100, Chris Wilson wrote: > Quoting Daniel Vetter (2020-05-11 10:54:33) > > - worse, neither vk nor gl (to my knowledge) have a concept of events > > for when the gpu died. The only stuff you have is things like > > arb_robustness which says a) everything continues as if nothing > > happened b) there's a function where you can ask whether your gl > > context and all the textures/buffers are toast. > > Vulkan/DX12 arrived after eGPU, and there is at least the concept of > VK_ERROR_DEVICE_LOST. Mainly used at the moment after a GPU hang and > loss of context. > > https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#devsandqueues-lost-device Ah cool, so -EIO on some ioctls, with silencing it in the gl driver and passing it on for the vk driver should be ok. Assuming vk frameworks bother to implement the *may* thing. I'm assuming if the validation midlayer doesn't inject this, it's untested and firework will ensue. But then more direct path to fireworks is what vk is all about :-) -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
