From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=38904 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PBmyM-00019b-7H for qemu-devel@nongnu.org; Fri, 29 Oct 2010 07:18:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PBmyK-0006hN-Uf for qemu-devel@nongnu.org; Fri, 29 Oct 2010 07:18:14 -0400 Received: from ozlabs.org ([203.10.76.45]:51347) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PBmyK-0006YZ-L6 for qemu-devel@nongnu.org; Fri, 29 Oct 2010 07:18:12 -0400 From: Rusty Russell Subject: Re: [Qemu-devel] Re: [PATCH] Implement a virtio GPU transport Date: Fri, 29 Oct 2010 21:48:00 +1030 References: <4CAC9CD1.2050601@collabora.co.uk> <4CBD7560.6080207@redhat.com> <4CC8226F.5080807@collabora.co.uk> In-Reply-To: <4CC8226F.5080807@collabora.co.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201010292148.01167.rusty@rustcorp.com.au> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: virtualization@lists.linux-foundation.org Cc: QEMU Developers , virtualization@lists.osdl.org, Ian Molton , Avi Kivity , linux-kernel@vger.kernel.org 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.