<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Launch of Qemu VM (with kvm/vfio/iommu/pci-stub) causes [drm:intel_uncore_check_errors] *ERROR* Unclaimed register before interrupt" href="https://bugs.freedesktop.org/show_bug.cgi?id=73834#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Launch of Qemu VM (with kvm/vfio/iommu/pci-stub) causes [drm:intel_uncore_check_errors] *ERROR* Unclaimed register before interrupt" href="https://bugs.freedesktop.org/show_bug.cgi?id=73834">bug 73834</a> from <a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> Ville Syrjala</a> <pre>VGA arbitration. Shudder. I tried to come up with a way to make it work somehow, and I apparently failed. I'm not going to try again any time soon. Here's what Daniel had to say when he reverted a bunch of VGA arbiter changes from the driver. You can follow the link to my stop_machine hack. commit ebff5fa9d545574324095d9c6a3cb80c9157abc5 Author: Dave Airlie <<a href="mailto:airlied@redhat.com">airlied@redhat.com</a>> Date: Fri Oct 11 15:12:04 2013 +1000 Revert "i915: Update VGA arbiter support for newer devices" This reverts commit 81b5c7bc8de3e6f63419139c2fc91bf81dea8a7d. Adding drm/i915 into the vga arbiter chain means that X (in a piece of well-meant paranoia) will do a get/put on the vga decoding around _every_ accel call down into the ddx. Which results in some nice performance disasters [1]. This really breaks userspace, by disabling DRI for everyone, and stops OpenGL from working, this isn't limited to just the i915 but both the integrated and discrete GPUs on multi-gpu systems, in other words this causes untold worlds of pain, Ville tried to come up with a Great Hack to fiddle the required VGA I/O ops behind everyone's back using stop_machine, but that didn't really work out [2]. Given that we're fairly late in the -rc stage for such games let's just revert this all. One thing we might want to keep is to delay the disabling of the vga decoding until the fbdev emulation and the fbcon screen is set up. If we kill vga mem decoding beforehand fbcon can end up with a white square in the top-left corner it tried to save from the vga memory for a seamless transition. And we have bug reports on older platforms which seem to match these symptoms. But again that's something to play around with in -next. References: [1] <a href="http://lists.x.org/archives/xorg-devel/2013-September/037763.html">http://lists.x.org/archives/xorg-devel/2013-September/037763.html</a> References: [2] <a href="http://www.spinics.net/lists/intel-gfx/msg34062.html">http://www.spinics.net/lists/intel-gfx/msg34062.html</a> Cc: Alex Williamson <<a href="mailto:alex.williamson@redhat.com">alex.williamson@redhat.com</a>> Cc: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>> Cc: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>> Signed-off-by: Dave Airlie <<a href="mailto:airlied@redhat.com">airlied@redhat.com</a>></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>