From: Rusty Russell <rusty@rustcorp.com.au>
To: virtualization@lists.linux-foundation.org
Cc: Ian Molton <ian.molton@collabora.co.uk>,
Avi Kivity <avi@redhat.com>,
virtualization@lists.osdl.org, linux-kernel@vger.kernel.org,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [PATCH] Implement a virtio GPU transport
Date: Fri, 29 Oct 2010 21:48:00 +1030 [thread overview]
Message-ID: <201010292148.01167.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4CC8226F.5080807@collabora.co.uk>
On Wed, 27 Oct 2010 11:30:31 pm Ian Molton wrote:
> On 19/10/10 11:39, Avi Kivity wrote:
> > On 10/19/2010 12:31 PM, Ian Molton wrote:
>
> >>> 2. should start with a patch to the virtio-pci spec to document what
> >>> you're doing
> >>
> >> Where can I find that spec?
> >
> > http://ozlabs.org/~rusty/virtio-spec/
>
> Ok, but I'm not patching that until theres been some review.
Fair enough; it's a bit of a PITA to patch, so it makes sense to get the
details nailed down first.
> There are links to the associated qemu and guest OS changes in my
> original email.
>
> >> It doesnt, at present... It could be changed fairly easily ithout
> >> breaking anything if that happens though.
> >
> > The hypervisor and the guest can be changed independently. The driver
> > should be coded so that it doesn't depend on hypervisor implementation
> > details.
>
> Fixed - updated patch tested and attached.
OK. FWIW, I think this is an awesome idea. 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 11:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4CAC9CD1.2050601@collabora.co.uk>
[not found] ` <4CB1D79A.6070805@redhat.com>
[not found] ` <4CBD739A.2010500@collabora.co.uk>
[not found] ` <4CBD7560.6080207@redhat.com>
2010-10-27 13:00 ` [Qemu-devel] Re: [PATCH] Implement a virtio GPU transport 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 [this message]
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=201010292148.01167.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=avi@redhat.com \
--cc=ian.molton@collabora.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--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).