drm/vmwgfx: Disable command buffers on svga3 without gbobjects
authorZack Rusin <zackr@vmware.com>
Fri, 18 Mar 2022 17:43:31 +0000 (13:43 -0400)
committerZack Rusin <zackr@vmware.com>
Fri, 13 May 2022 14:29:36 +0000 (10:29 -0400)
commit21d1d192890ced87f2f04f8f4dea92406e0b162a
treece8791d7992270188198a8dd0b433e71f56b17c9
parent3059d9b9f6aa433a55b9d0d21b566396d5497c33
drm/vmwgfx: Disable command buffers on svga3 without gbobjects

With very limited vram on svga3 it's difficult to handle all the surface
migrations. Without gbobjects, i.e. the ability to store surfaces in
guest mobs, there's no reason to support intermediate svga2 features,
especially because we can fall back to fb traces and svga3 will never
support those in-between features.

On svga3 we wither want to use fb traces or screen targets
(i.e. gbobjects), nothing in between. This fixes presentation on a lot
of fusion/esxi tech previews where the exposed svga3 caps haven't been
finalized yet.

Signed-off-by: Zack Rusin <zackr@vmware.com>
Fixes: 2cd80dbd3551 ("drm/vmwgfx: Add basic support for SVGA3")
Cc: <stable@vger.kernel.org> # v5.14+
Reviewed-by: Martin Krastev <krastevm@vmware.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20220318174332.440068-5-zack@kde.org
drivers/gpu/drm/vmwgfx/vmwgfx_cmd.c