Announcement

Collapse
No announcement yet.

Gfxstream Merged Into Mesa For Vulkan Virtualization

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Gfxstream Merged Into Mesa For Vulkan Virtualization

    Phoronix: Gfxstream Merged Into Mesa For Vulkan Virtualization

    After seven months under review, Google's Gfxstream code has been upstreamed into Mesa 24.3 as a Vulkan virtualization solution...

    Gfxstream Merged Into Mesa For Vulkan Virtualization - Phoronix
    https://www.phoronix.com/news/Mesa-Gfxstream-Merged
    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
    Tags: None
    • Likes 2
  • #2
    I was going to say SpectrumOS might find this handy but just realized they've replaced CrosVM with Cloud Hypervisor

    Comment

    • #3
      Proxmox, I'm looking at you.
      • Likes 4

      Comment

      • #4
        It would be nice to see some proper benchmarks between this and venus
        • Likes 4

        Comment

        • #5
          It'll be very cool to see the combination of this and MS adopting SPIR-V in place of DXIL. That makes at least one part of the equation easier.
          • Likes 1

          Comment

          • #6
            What about a Windows driver for hardware accelerated Windows guests?

            Comment

            • #7
              Originally posted by microcode View Post
              It'll be very cool to see the combination of this and MS adopting SPIR-V in place of DXIL. That makes at least one part of the equation easier.
              mesa has already had virgl venus for a while

              Comment

              • #8
                Originally posted by Quackdoc View Post
                mesa has already had virgl venus for a while
                I think you're missing the point; this change means that SPIR-V will be, by definition, complete for DirectX shader programs; which is not currently the case. This means that the host can take on the task of supporting these extensions, and workarounds/fills will be less required. Currently there's a lot of work involved in translating current DirectX onto virtio-gpu hosts, which is one of the reasons there is no adequate D3D virgl driver for Windows yet.

                Comment

                • #9
                  Originally posted by microcode View Post
                  I think you're missing the point; this change means that SPIR-V will be, by definition, complete for DirectX shader programs; which is not currently the case. This means that the host can take on the task of supporting these extensions, and workarounds/fills will be less required. Currently there's a lot of work involved in translating current DirectX onto virtio-gpu hosts, which is one of the reasons there is no adequate D3D virgl driver for Windows yet.
                  Im not sure how this related to gfxstream

                  Comment

                  Previous template Next
                  Working...
                  X