[Spice-commits] Changes to 'rhel.master'

[Alon Levy]

New branch 'rhel.master' available with the following commits:
commit 5072d57f1da77ed024c7ca492a56251fab34f7c6
Author: Alon Levy <alevy at redhat.com>
Date:   Wed Jul 17 16:38:04 2013 +0300

    xddm/miniport/qxl.inf: bump version and touch date
    
    We haven't done this for most any change. Perhaps we should do this? No
    idea what the x.y.z.w convention is, so I made the most minor change
    right now. But the date is the important bit.
    
    (cherry picked from commit ab746740d03eb3c2494f7a70971861b933688718)

commit 1c46e6fe756fce0ed87b23fd74e10d9e47380a5d
Author: Alon Levy <alevy at redhat.com>
Date:   Wed Jul 17 15:28:54 2013 +0300

    miniport: disable surfaces by default
    
    Change the registry checking logic we already have, instead of enabling
    surfaces by default we now disable surfaces by default. They can be
    enabled without driver change by creating a registry key name
    "SurfacesEnabled" of type DWORD with any value under the adapter key.
    
    To find the adapter key, one way is looking for the key under which
    there is a value of name "QxlDeviceID" after a successfull startup of
    the qxl driver.
    
    RHBZ: 985408
    (cherry picked from commit 154c477005c8f5001262123ddc043adba1b4bf0e)

commit 843bb391f01665ce21756b05d05b221c4246877a
Author: Yonit Halperin <yhalperi at redhat.com>
Date:   Fri Jul 5 11:14:25 2013 -0400

    display: apply the fix in fc314927bc48835e to Alpha Bitmaps
    
    rhbz#968050
    
    In contrast to Microsoft Msdn documentation, the iUniq of a SURFOBJ doesn't
    always change when the surface changes. However, it seems that the
    iUniq of the associated color_trans (XLATEOBJ) changes, while its
    flXlate=XO_TRIVIAL. Since we tried to retrieve the alpha bitmap key
    only by the surface iUniq, we fetched the wrong bitmap, and it looked
    like parts of the screen haven't been rendered.
    
    The patch modifies QXLGetAlphaBitmap so that it will use GetCacheImage
    instead of duplicating its code. GetCacheImage was already fixed in
    fc314927bc48835e to combine the iUniq of the surace and the
    color_trans.
    
    (cherry picked from commit 170af9c620d40e607b02f9722bc90260c15ed914)

commit 855607b9daa44cb24ceaaf27f1de7aa51d509919
Author: Alon Levy <alevy at redhat.com>
Date:   Sun Jun 30 18:43:52 2013 +0300

    miniport/qxl.c: fail a custom mode that would not fit memory (RHBZ#863488)
    
    Signed-off-by: Alon Levy <alevy at redhat.com>
    (cherry picked from commit 85de1534831a63ebcb682a10d4cd509467f4e5d0)

commit adb0148d6eadf68668d9994078515453070b2919
Author: Yonit Halperin <yhalperi at redhat.com>
Date:   Fri Jun 21 08:39:28 2013 -0400

    display: fix deadlock when dbg_level >= 15
    
    DebugPrintV first locks print_sem, and then locks io_sem.
    async_io, locks io_sem.
    In ordr to avoid a deadlock, DebugPrintV MUSTN'T be called when
    io_sem is locked.
    I also moved the locking of io_sem, so that reading pdev->use_async
    will also be protected (async_io can modify use_async to 0 upon a
    timeout).
    
    Also notice, that locking io_sem during DebugPrintV limits our ability
    to use the log_port for debugging concurrency problems related to ios.
    
    (cherry picked from commit ae74511ef2269491347f0b2f78f94dcabed268b9)

commit 734d8a0224649295431add7f300933b41ccd9ca2
Author: Yonit Halperin <yhalperi at redhat.com>
Date:   Fri Jun 21 08:37:58 2013 -0400

    display: handle correctly bitmaps with line-size > 64K
    
    rhbz#966835
    
    We do not support copying such bitmaps. But instead of failing
    operations that involve such bitmaps we either BSODed (in checked
    builds), or proceeded with the bitmap copying (in free builds) - this lead to an infinite
    loop allocating QXLDataChunks without any data, just header.
    
    (cherry picked from commit 0a2458574d3c22314ff58758ad98c820374de370)