intel: fix fullscreen damage posting on pageflip
PATCH 1/1 intel: fix fullscreen damage posting on pageflip
From: Dave Airlie <[email protected]>
While playing with MPX and sw cursor I noticed page flips won't end up misrendering some bits, so the sw cursor was replacing the bits on the wrong pixmap.
Fix the damage handling to be correct and append damage before swapping the pointers and process damage after.
This fixes misrendering with MPX cursors under a fullscreen compositor, that pageflips.
--- src/intel_dri.c | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-)
src/intel_dri.c +12 -13
@@ -725,6 +725,17 @@ static struct intel_pixmap * intel_exchange_pixmap_buffers(struct intel_screen_private *intel, PixmapPtr front, PixmapPtr back) { struct intel_pixmap *new_front, *new_back; +RegionRec region; + +/* Post damage on the front buffer so that listeners, such +* as DisplayLink know take a copy and shove it over the USB. +* also for sw cursors. +*/ + region.extents.x1 = region.extents.y1 =0 ; + region.extents.x2 = front->drawable.width; + region.extents.y2 = front->drawable.height; + region.data =NULL ; +DamageRegionAppend (&front->drawable, ®ion); new_front =intel_get_pixmap_private (back); new_back =intel_get_pixmap_private (front);
@@ -735,19 +746,7 @@ intel_exchange_pixmap_buffers(struct intel_screen_private *intel, PixmapPtr fronintel_glamor_exchange_buffers (intel, front, back); -/* Post damage on the new front buffer so that listeners, such -* as DisplayLink know take a copy and shove it over the USB. -*/ - { -RegionRec region; - - region.extents.x1 = region.extents.y1 =0 ; - region.extents.x2 = front->drawable.width; - region.extents.y2 = front->drawable.height; - region.data =NULL ; -DamageRegionAppend (&front->drawable, ®ion); -DamageRegionProcessPending (&front->drawable); - } +DamageRegionProcessPending (&front->drawable);return new_front; }
Signature · 1 line
1.7.12.1
Quoted 11 lines · Dave Airlie
From: Dave Airlie <[email protected]>
While playing with MPX and sw cursor I noticed page flips won't end up misrendering some bits, so the sw cursor was replacing the bits on the wrong pixmap.
Fix the damage handling to be correct and append damage before swapping the pointers and process damage after.
This fixes misrendering with MPX cursors under a fullscreen compositor, that pageflips.
Wow, what magic is this? The created region is the same and front->drawable left unmodified by the exchange. The exchange only manipulates the devPrivates and has not other side effects. The only uncertain quantity there is the intel_glamor_exchange_buffers()...
So the change is that we append the same damage to the same drawable earlier, yet still process that damage at the same time, with no apparent side-effects between the two operations. I'm just not understanding why this has any effect.
-Chris
Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre
Quoted 18 lines · Chris Wilson
Quoted 11 lines · Dave Airlie
From: Dave Airlie <[email protected]>
While playing with MPX and sw cursor I noticed page flips won't end up misrendering some bits, so the sw cursor was replacing the bits on the wrong pixmap.
Fix the damage handling to be correct and append damage before swapping the pointers and process damage after.
This fixes misrendering with MPX cursors under a fullscreen compositor, that pageflips.
Wow, what magic is this? The created region is the same and
front->drawableleft unmodified by the exchange. The exchange only manipulates the devPrivates and has not other side effects. The only uncertain quantity there is theintel_glamor_exchange_buffers()...
Quoted 4 lines
So the change is that we append the same damage to the same drawable earlier, yet still process that damage at the same time, with no apparent side-effects between the two operations. I'm just not understanding why this has any effect.
Hence why I didn't do it right in the first place, I thought I understood how damage worked :-)
We have pre-rendering damage reporting and post-rendering damage reporting!, so sw cursors really wants it before the fact so it can copy the area out underneath itself,
damage append will process the pre-damage stuff, and pending will process post-damage hooks.
Dave.
Quoted 27 lines · Dave Airlie
Quoted 18 lines · Chris Wilson
Quoted 11 lines · Dave Airlie
From: Dave Airlie <[email protected]>
While playing with MPX and sw cursor I noticed page flips won't end up misrendering some bits, so the sw cursor was replacing the bits on the wrong pixmap.
Fix the damage handling to be correct and append damage before swapping the pointers and process damage after.
This fixes misrendering with MPX cursors under a fullscreen compositor, that pageflips.
Wow, what magic is this? The created region is the same and
front->drawableleft unmodified by the exchange. The exchange only manipulates the devPrivates and has not other side effects. The only uncertain quantity there is theintel_glamor_exchange_buffers()...Quoted 4 lines
So the change is that we append the same damage to the same drawable earlier, yet still process that damage at the same time, with no apparent side-effects between the two operations. I'm just not understanding why this has any effect.
Hence why I didn't do it right in the first place, I thought I understood how damage worked :-)
Quoted 6 lines
We have pre-rendering damage reporting and post-rendering damage reporting!, so sw cursors really wants it before the fact so it can copy the area out underneath itself,
damage append will process the pre-damage stuff, and pending will process post-damage hooks.
Thanks for the explanation, I had forgotten that not everything was PostOp reported!
commit dadffd0061e2b14db397608e3cedfe9c76e546c8
Author: Dave Airlie <[email protected]> Date: Thu Oct 11 14:30:29 2012 +1000
intel: fix fullscreen damage posting on pageflip
-Chris
Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre