From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: virtualization@lists.osdl.org,
Ian Molton <ian.molton@collabora.co.uk>,
linux-kernel@vger.kernel.org,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [PATCH] Implement a virtio GPU transport
Date: Mon, 01 Nov 2010 08:21:38 -0500 [thread overview]
Message-ID: <4CCEBEE2.8010404@codemonkey.ws> (raw)
In-Reply-To: <4CCE9989.2010809@redhat.com>
On 11/01/2010 05:42 AM, Avi Kivity wrote:
> On 10/28/2010 03:52 PM, Ian Molton wrote:
>> 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.
>
> Waiting for a response is fine, but can't the guest issue a second
> batch while waiting for the first?
In a threaded application I think you mean but all RPCs are dispatched
holding a global lock so even within a threaded application, only a
single GL call will be executed at a time.
The other scenario would be multiple applications trying to use GL but
AFAICT, this is not supported in the current model.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-11-01 13:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4CAC9CD1.2050601@collabora.co.uk>
[not found] ` <4CB1D79A.6070805@redhat.com>
2010-10-19 10:31 ` [Qemu-devel] Re: [PATCH] Implement a virtio GPU transport Ian Molton
2010-10-19 10:39 ` Avi Kivity
2010-10-27 13:00 ` Ian Molton
2010-10-28 9:27 ` Avi Kivity
2010-10-28 11:54 ` Ian Molton
2010-10-28 14:24 ` Avi Kivity
2010-10-28 14:43 ` Anthony Liguori
2010-10-28 19:50 ` Ian Molton
2010-10-28 20:14 ` Anthony Liguori
2010-10-28 21:41 ` Ian Molton
2010-10-28 19:52 ` Ian Molton
2010-11-01 10:42 ` Avi Kivity
2010-11-01 13:21 ` Anthony Liguori [this message]
2010-11-01 15:49 ` Ian Molton
2010-11-01 15:57 ` Anthony Liguori
2010-11-03 17:49 ` Ian Molton
2010-11-01 15:50 ` Ian Molton
2010-10-29 11:18 ` Rusty Russell
2010-10-29 11:49 ` Ed Tomlinson
2010-10-29 13:05 ` Anthony Liguori
2010-11-01 11:53 ` Alon Levy
2010-11-01 13:28 ` Anthony Liguori
2010-11-03 18:03 ` Ian Molton
2010-11-03 18:17 ` Anthony Liguori
2010-11-05 18:05 ` Ian Molton
2010-11-10 17:22 ` Ian Molton
2010-11-10 17:47 ` Anthony Liguori
2010-11-12 12:14 ` Ian Molton
2010-11-12 13:21 ` Anthony Liguori
2010-11-04 9:13 ` Alon Levy
2010-11-05 17:57 ` Ian Molton
2010-11-03 17:50 ` Ian Molton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CCEBEE2.8010404@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=ian.molton@collabora.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).