[Bug 59539] Frame rate drops significantly when changing monitor resolution for plugable hardware

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=59539

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
Ah, the issue is that pixregion is only clipped inside PixmapSyncDirtyHelper()
and so without performing the clipping ourselves we cannot get the dirty
ordering right. So,

commit 828a3a80aa3f0692e7be2831d58bccf02e2c481d
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Fri Jan 18 13:16:23 2013 +0000

    uxa: Clip dirty region to slave pixmap before appending damage

    Fixes regression from

    commit c789d06cf8a0debc67058d7be1483f5b542e2baa
    Author: Dave Airlie <airlied at redhat.com>
    Date:   Mon Jan 7 13:57:21 2013 +1000

        intel: fixup damage posting to be done correctly around slave pixmap

    which causes the entire slave scanout to be readback from uncached
    memory every time a pixel is modified.

    Reported-by: Stephen Liang <inteldriver at angrywalls.com>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=59539
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130118/cff48b13/attachment.html>