Announcement

Collapse
No announcement yet.

Mesa 20.0's RADV Driver Deems Navi/GFX10 Stable, Vulkan 1.2 In Good Shape, ACO Fixes

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mesa 20.0's RADV Driver Deems Navi/GFX10 Stable, Vulkan 1.2 In Good Shape, ACO Fixes

    Phoronix: Mesa 20.0's RADV Driver Deems Navi/GFX10 Stable, Vulkan 1.2 In Good Shape, ACO Fixes

    With Mesa 20.0 scheduled for branching today (though that could be delayed a few days potentially depending upon last minute requests), there's been a flurry of Radeon Vulkan "RADV" driver activity to squeeze into this first Mesa release series of 2020...

    http://www.phoronix.com/scan.php?pag...DV-Fixes-Final

  • #2
    I wonder if anyone working on making amdgpu ddx driver survive gpu resets...

    Comment


    • #3
      Originally posted by khnazile View Post
      I wonder if anyone working on making amdgpu ddx driver survive gpu resets...
      afair driver survives reset, but videomemory is cleared and apps are not prepared to refill it

      Comment


      • #4
        Originally posted by pal666 View Post
        afair driver survives reset, but videomemory is cleared and apps are not prepared to refill it
        OpenGL should get texture volatility features (like Direct3D), and the driver should attempt to recover as much memory as possible after the reset, if the card retains its memory after it.

        Comment


        • #5
          Originally posted by pal666 View Post
          afair driver survives reset, but videomemory is cleared and apps are not prepared to refill it
          I'm not sure about that. Reset did work for older videocards with radeon driver, when it didn't use glamor. But these days, when gpu reset occurs, everything dies, even apps that don't use any hw accelerated rendering, because the X driver uses EGL.

          Comment


          • #6
            yayy more AMD Fake Vulkan 1.2 support

            Comment


            • #7
              Originally posted by tildearrow View Post

              OpenGL should get texture volatility features (like Direct3D), and the driver should attempt to recover as much memory as possible after the reset, if the card retains its memory after it.
              The driver already supports the GL robustness extensions. The xserver or desktop compositor needs to add support for the OpenGL robustness extensions so that they can get notified of GPU reset and properly re-initialize it's GPU context. On windows the desktop manager does something similar using the DX equivalent.

              Comment


              • #8
                Originally posted by agd5f View Post

                The driver already supports the GL robustness extensions. The xserver or desktop compositor needs to add support for the OpenGL robustness extensions so that they can get notified of GPU reset and properly re-initialize it's GPU context. On windows the desktop manager does something similar using the DX equivalent.
                Yes on Windows you get that infamous "Display Driver Stopped Responding and has Recovered" error dialog. Obviously in Linux we don't see that, maybe except noticing that screen graphics may be corrupted or display simply goes black when ddx hangs/crashes. Would be good if X has a way to gracefully recover from a graphics device hang or crash.

                Comment


                • #9
                  Originally posted by DeepDayze View Post
                  Would be good if X has a way to gracefully recover from a graphics device hang or crash.
                  Right. That's what I just described. The xserver or compositor (for non-X desktops) needs to make use of the GL robustness extensions to handle this gracefully.

                  Comment


                  • #10
                    Originally posted by tildearrow View Post
                    the driver should attempt to recover as much memory as possible after the reset, if the card retains its memory after it.
                    does your computer retain memory after reset?

                    Comment

                    Working...
                    X