Remove the unnecessary MI_FLUSH from the flush handler
The kernel will emit any required flushes between the dri client and the ddx, and we do not rely on the MI_FLUSH here for scanout. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
This commit is contained in:
parent
79444291a3
commit
ced747cefb
|
|
@ -757,17 +757,8 @@ intel_flush_callback(CallbackListPtr *list,
|
|||
pointer user_data, pointer call_data)
|
||||
{
|
||||
ScrnInfoPtr scrn = user_data;
|
||||
intel_screen_private *intel = intel_get_screen_private(scrn);
|
||||
|
||||
if (scrn->vtSema) {
|
||||
/* Emit a flush of the rendering cache, or on the 965
|
||||
* and beyond rendering results may not hit the
|
||||
* framebuffer until significantly later.
|
||||
*/
|
||||
intel_batch_submit(scrn,
|
||||
intel->need_mi_flush ||
|
||||
!list_is_empty(&intel->flush_pixmaps));
|
||||
}
|
||||
if (scrn->vtSema)
|
||||
intel_batch_submit(scrn, FALSE);
|
||||
}
|
||||
|
||||
#if HAVE_UDEV
|
||||
|
|
|
|||
Loading…
Reference in New Issue