From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Molton Subject: Re: [Qemu-devel] Re: [PATCH] Implement a virtio GPU transport Date: Thu, 28 Oct 2010 20:52:18 +0100 Message-ID: <4CC9D472.2080109@collabora.co.uk> References: <4CAC9CD1.2050601@collabora.co.uk> <4CB1D79A.6070805@redhat.com> <4CBD739A.2010500@collabora.co.uk> <4CBD7560.6080207@redhat.com> <4CC8226F.5080807@collabora.co.uk> <4CC94203.1080207@redhat.com> <4CC9647A.50108@collabora.co.uk> <4CC98784.7020907@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4CC98784.7020907@redhat.com> Sender: linux-kernel-owner@vger.kernel.org To: Avi Kivity Cc: virtualization@lists.osdl.org, linux-kernel@vger.kernel.org, QEMU Developers List-Id: virtualization@lists.linuxfoundation.org On 28/10/10 15:24, Avi Kivity wrote: >> The caller is intended to block as the host must perform GL rendering >> before allowing the guests process to continue. > > Why is that? Can't we pipeline the process? No, not really. the guest may call for the scene to be rendered at any time and we have to wait for that to happen before we can return the data to it. -Ian