• Thomas Hellstrom's avatar
    drm/vmwgfx: Restart command buffers after errors · 65b97a2b
    Thomas Hellstrom authored
    Previously we skipped the command buffer and added an extra fence to
    avoid hangs due to skipped fence commands.
    Now we instead restart the command buffer after the failing command,
    if there are any commands left.
    In addition we print out some information about the failing command
    and its location in the command buffer.
    
    Testing Done: ran glxgears using mesa modified to send the NOP_ERROR
    command before each 10th clear and verified that we detected the device
    error properly and that there were no other device errors caused by
    incorrectly ordered command buffers. Also ran the piglit "quick" test
    suite which generates a couple of device errors and verified that
    they were handled as intended.
    Signed-off-by: default avatarThomas Hellstrom <thellstrom@vmware.com>
    Reviewed-by: default avatarBrian Paul <brianp@vmware.com>
    Reviewed-by: default avatarSinclair Yeh <syeh@vmware.com>
    65b97a2b
vmwgfx_execbuf.c 129 KB