[Bug 111004] memcpy accessing GPU memory mappings using SSE instructions breaks in KVM

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Jun 27 08:17:49 UTC 2019


Michel Dänzer <michel at daenzer.net> changed:

           What    |Removed                     |Added
           Assignee|xorg-driver-ati at lists.x.org |mesa-dev at lists.freedesktop.
                   |                            |org
            Summary|X crash in memcpy (RX590)   |memcpy accessing GPU memory
                   |                            |mappings using SSE
                   |                            |instructions breaks in KVM
          Component|Driver/AMDgpu               |Other
         QA Contact|xorg-team at lists.x.org       |mesa-dev at lists.freedesktop.
                   |                            |org
            Version|unspecified                 |git
            Product|xorg                        |Mesa

--- Comment #7 from Michel Dänzer <michel at daenzer.net> ---
Reassigning to Mesa, but TBH I wouldn't expect anything to happen anytime soon
(unless you do it yourself). Mesa definitely wants to use an optimized memcpy
on bare metal, so replacing memcpy everywhere is probably out of the question,
and finding all code in Mesa where this could happen might be tricky.

Also note that APIs such as OpenGL or Vulkan expose such GPU mappings to
applications directly, so the approach you're suggesting would likely require
fixing a lot of application/framework code as well. It would most likely be
less painful if this could be solved in KVM somehow, or if you just override
the default memcpy implementation (with a known-good one) on your system.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.x.org/archives/xorg-driver-ati/attachments/20190627/85ea4a34/attachment.html>

More information about the xorg-driver-ati mailing list