[Bug 105721] [g33] piglit intermittent failure on spec.apple_object_purgeable.object_purgeable-api-vbo

[bugzilla-daemon at freedesktop.org]

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

--- Comment #1 from Chris Wilson <chris at chris-wilson.co.uk> ---
Fwiw, pull the fixes from i965:

commit ed442ee39b4e2a2e25ea4ccd880e4bded9d29a51
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Tue Jan 10 21:23:24 2017 +0000

    i965: Do not use purged bo after calling glObjectUnpurgeable

    If the buffer has been freed by the kernel under memory pressure, it is
    invalid to try and access the backing storage for that buffer in the
    future - the backing storage is not recreated automatically. As such we
    need to mark the GL object as being freed for unretained buffers and so
    recreate the object on next use.

    Futhermore from the GL_APPLE_object_purgeable:

        "In contrast, by calling ObjectUnpurgeableAPPLE with an <option> of
        UNDEFINED_APPLE, the application is indicating that it intends to
        recreate the contents of the storage from scratch.  Further, the
        application is is stating that it would like the GL to do only the
        minimal amount of work set PURGEABLE_APPLE to FALSE.   If
        ObjectUnpurgeableAPPLE is called with the <option> set to
        UNDEFINED_APPLE, then ObjectUnpurgeableAPPLE will return the value
        UNDEFINED_APPLE."

    we must always report GL_UNDEFINED_APPLE when called with
    glObjectUnpurgeable(GL_UNDEFINED_APPLE).

    Testcase: piglit/object_purgeable-api-*
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Reviewed-by: Kenneth Graunke <kenneth at whitecape.org>

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180326/bc40bd65/attachment.html>