From: Thomas Hellstrom <thellst...@vmware.com> Sometimes it appears like the device modifies the command header offset member. So explicitly clear it when restarting after an error.
Signed-off-by: Thomas Hellstrom <thellst...@vmware.com> Reviewed-by: Sinclair Yeh <s...@vmware.com> --- drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c b/drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c index a916864..ce92198 100644 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c @@ -563,6 +563,7 @@ static void vmw_cmdbuf_work_func(struct work_struct *work) entry->cmd += new_start_offset; cb_hdr->length -= new_start_offset; cb_hdr->errorOffset = 0; + cb_hdr->offset = 0; list_add_tail(&entry->list, &restart_head[entry->cb_context]); man->ctx[entry->cb_context].block_submission = true; } -- 2.7.4 _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel