Re: [iGVT-g] Ask for comments of getting guest framebuffer in igvt-g

From: Gerd Hoffmann <kraxel@redhat.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "igvt-g@lists.01.org" <igvt-g@ml01.01.org>,
	"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Cowperthwaite, David J" <david.j.cowperthwaite@intel.com>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: [iGVT-g] Ask for comments of getting guest framebuffer in igvt-g
Date: Tue, 08 Mar 2016 09:36:42 +0100	[thread overview]
Message-ID: <1457426202.22567.40.camel@redhat.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F7DEF00@SHSMSX101.ccr.corp.intel.com>

  Hi,

> btw I don't think this vblank issue would be very significant. The main
> targeted usage of GVT-g is for server virtualization/cloud, where 
> a remoting protocol is required for customer to see the content through
> network.

The plan for that is to let the gpu video encoder process the guest
framebuffer.  So the video encoder still being busy processing the
buffer while the guest already started updating it can certainly lead to
visible tearing.

I think using vblank to signal the guest when the host is done
processing the framebuffer makes sense.  It'll simply throttle the guest
in case the host is too busy to keep up.

Storing the guest framebuffer via blit somewhere else, just to allow the
guest render at full frame rate even if the host isn't able to process
the frames fast enough looks pointless to me.  We are simply wasting gpu
cycles then.

cheers,
  Gerd

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx