From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:40721) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QV0bI-0008AA-AF for qemu-devel@nongnu.org; Fri, 10 Jun 2011 08:14:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QV0bD-0006Xi-NF for qemu-devel@nongnu.org; Fri, 10 Jun 2011 08:14:08 -0400 Received: from mail-vw0-f45.google.com ([209.85.212.45]:34195) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QV0bD-0006Xe-CC for qemu-devel@nongnu.org; Fri, 10 Jun 2011 08:14:03 -0400 Received: by vws17 with SMTP id 17so2393772vws.4 for ; Fri, 10 Jun 2011 05:14:03 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <87lix9dioo.fsf@rustcorp.com.au> References: <4DEE2B15.4090809@redhat.com> <87lixbgax9.fsf@rustcorp.com.au> <4DF06F4F.8050308@redhat.com> <87lix9dioo.fsf@rustcorp.com.au> Date: Fri, 10 Jun 2011 13:14:02 +0100 Message-ID: From: Stefan Hajnoczi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] virtio scsi host draft specification, v3 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Christoph Hellwig , Stefan Hajnoczi , "kvm@vger.kernel.org" , "Michael S. Tsirkin" , Rusty Russell , qemu-devel , Linux Kernel Mailing List , Hannes Reinecke , Linux Virtualization On Fri, Jun 10, 2011 at 12:33 PM, Rusty Russell wro= te: > On Thu, 09 Jun 2011 08:59:27 +0200, Paolo Bonzini w= rote: >> On 06/09/2011 01:28 AM, Rusty Russell wrote: >> >> > =A0after some preliminary discussion on the QEMU mailing list, I pr= esent a >> >> > =A0draft specification for a virtio-based SCSI host (controller, HB= A, you >> >> > =A0name it). >> > >> > OK, I'm impressed. =A0This is very well written and it doesn't make an= y of >> > the obvious mistakes wrt. virtio. >> >> Thanks very much, and thanks to those who corrected my early mistakes. >> >> > I assume you have an implementation, as well? >> >> Unfortunately not; "we're working on it", which means I should start in >> July when I come back from vacation. >> >> Do you prefer to wait for one before I make a patch to the LyX source? >> In the meanwhile, can you reserve a subsystem ID for me? >> >> Paolo > > Sure, you can have the next subsystem ID. > > It's a pain to patch once it's in LyX, so let's get the implementation > base on what you posted here an see how much it changes first... Paolo, I'll switch the Linux guest LLD and QEMU virtio-scsi skeleton that I have to comply with the spec. Does this sound good or did you want to write these from scratch? Stefan