From 1e443c4717a8b107c0c9283e222482703ac0f358 Mon Sep 17 00:00:00 2001 From: Thomas Hellstrom Date: Wed, 25 Feb 2015 01:51:11 -0800 Subject: vmware/vmwgfx: Try to use only_hw_present semantics if screen targets are enabled If screen targets are enabled and there is a reasonable chance that the vmwgfx drm driver can use the surface backing a pixmap as a screen target surface, then make that surface a modesetting framebuffer rather than the corresponding DMA buffer. In practice this applies when we start scanning out from the origin (0,0) of the pixmap. However, we would also like to apply the constraint that the scanout area is the entire pixmap, since that is the constraint used by the drm driver, but that would currently require drm framebuffer reallocations and possible flicker, so disable that for now. The drm driver will correctly handle the possibly oversized surface handed to it anyway, and the cost we pay for this is an extra hardware copy of the dirtied area when doing a software update of the scanout. Signed-off-by: Thomas Hellstrom Reviewed-by: Sinclair Yeh --- vmwgfx/vmwgfx_driver.h | 1 + 1 file changed, 1 insertion(+) (limited to 'vmwgfx/vmwgfx_driver.h') diff --git a/vmwgfx/vmwgfx_driver.h b/vmwgfx/vmwgfx_driver.h index 31dfc0f..b57d523 100644 --- a/vmwgfx/vmwgfx_driver.h +++ b/vmwgfx/vmwgfx_driver.h @@ -115,6 +115,7 @@ typedef struct _modesettingRec Bool only_hw_presents; MessageType from_hwp; Bool isMaster; + Bool has_screen_targets; /* Broken-out options. */ -- cgit v1.2.3