From: Anthony Liguori <anthony@codemonkey.ws>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Ian Molton <ian.molton@collabora.co.uk>,
QEMU Developers <qemu-devel@nongnu.org>,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org,
Avi Kivity <avi@redhat.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] Re: [PATCH] Implement a virtio GPU transport
Date: Fri, 29 Oct 2010 08:05:19 -0500 [thread overview]
Message-ID: <4CCAC68F.7050903@codemonkey.ws> (raw)
In-Reply-To: <201010292148.01167.rusty@rustcorp.com.au>
On 10/29/2010 06:18 AM, Rusty Russell wrote:
>> Fixed - updated patch tested and attached.
>>
> OK. FWIW, I think this is an awesome idea.
Paravirtual OpenGL or the actual proposed implementation? Have you
looked at the actual code?
If I understand correctly, the implementation is an RPC of opengl
commands across virtio that are then rendered on the host to an
offscreen buffer. The buffer is then sent back to the guest in rendered
form.
But it's possible to mess around with other guests because the opengl
commands are not scrubbed. There have been other proposals in the past
that include a mini JIT that would translate opengl commands into a safe
form.
Exposing just an opengl RPC transport doesn't seem that useful either.
It ought to be part of a VGA card in order for it to be integrated with
the rest of the graphics system without a round trip.
The alternative proposal is Spice which so far noone has mentioned.
Right now, Spice seems to be taking the right approach to guest 3d support.
Regards,
Anthony Liguori
> I understand others are skeptical,
> but this seems simple and if it works and you're happy to maintain it I'm
> happy to let you do it :)
>
> Cheers,
> Rusty.
>
>
next prev parent reply other threads:[~2010-10-29 13:10 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
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 [this message]
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=4CCAC68F.7050903@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=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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).