OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Revert "intel: Use the new DRI2 flush invalidate entrypoint to signal frame done."

Browse Source 
This reverts commit 7d4e674b21.  It broke
throttling in the non-new-DRI2 case.
This commit is contained in:
Eric Anholt
2010-01-25 14:48:57 -08:00
parent 5e1851b144
commit c7fc9bfb22
2 changed files with 20 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
src/mesa/drivers/dri/intel/intel_screen.c
View File

@@ -126,29 +126,8 @@ intelDRI2Flush(__DRIdrawable *drawable)
static void
intelDRI2FlushInvalidate(__DRIdrawable *drawable)
{
struct intel_context *intel = drawable->driContextPriv->driverPrivate;
intelDRI2Flush(drawable);
drawable->validBuffers = GL_FALSE;
/* We're using FlushInvalidate as an indicator that a frame is
* done. It's only called immediately after SwapBuffers, so it
* won't affect front-buffer rendering or applications explicitly
* managing swap regions using MESA_copy_buffer.
*
* Wait for the swapbuffers before the one we just emitted, so we don't
* get too many swaps outstanding for apps that are GPU-heavy but not
* CPU-heavy.
*
* Unfortunately, we don't have a handle to the batch containing the swap,
* and getting our hands on that doesn't seem worth it, so we just use the
* first batch we emitted after the last swap.
*/
if (intel->first_post_swapbuffers_batch != NULL) {
drm_intel_bo_wait_rendering(intel->first_post_swapbuffers_batch);
drm_intel_bo_unreference(intel->first_post_swapbuffers_batch);
intel->first_post_swapbuffers_batch = NULL;
}
}
static const struct __DRI2flushExtensionRec intelFlushExtension = {