From: Rusty Russell <rusty@rustcorp.com.au>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Christoph Hellwig <chellwig@redhat.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>,
Linux Virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [Qemu-devel] virtio scsi host draft specification, v3
Date: Fri, 10 Jun 2011 21:03:59 +0930 [thread overview]
Message-ID: <87lix9dioo.fsf@rustcorp.com.au> (raw)
In-Reply-To: <4DF06F4F.8050308@redhat.com>
On Thu, 09 Jun 2011 08:59:27 +0200, Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 06/09/2011 01:28 AM, Rusty Russell wrote:
> >> > after some preliminary discussion on the QEMU mailing list, I present a
> >> > draft specification for a virtio-based SCSI host (controller, HBA, you
> >> > name it).
> >
> > OK, I'm impressed. This is very well written and it doesn't make any 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...
Cheers,
Rusty.
next prev parent reply other threads:[~2011-06-10 11:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 13:43 [Qemu-devel] virtio scsi host draft specification, v3 Paolo Bonzini
2011-06-08 23:28 ` Rusty Russell
2011-06-09 6:59 ` Paolo Bonzini
2011-06-10 11:33 ` Rusty Russell [this message]
2011-06-10 12:14 ` Stefan Hajnoczi
2011-06-10 12:22 ` Paolo Bonzini
2011-06-10 12:55 ` Hannes Reinecke
2011-06-10 14:35 ` Paolo Bonzini
2011-06-14 8:39 ` Hannes Reinecke
2011-06-14 15:53 ` Stefan Hajnoczi
2011-06-29 8:33 ` Paolo Bonzini
2011-06-29 9:39 ` Stefan Hajnoczi
2011-06-29 10:07 ` Christoph Hellwig
2011-06-29 10:23 ` Hannes Reinecke
2011-06-29 10:27 ` Christoph Hellwig
2011-07-01 6:41 ` Paolo Bonzini
2011-07-01 7:14 ` Hannes Reinecke
2011-07-01 8:35 ` Paolo Bonzini
2011-07-04 13:38 ` Hai Dong,Li
2011-07-04 14:22 ` Stefan Hajnoczi
2011-06-12 7:51 ` Michael S. Tsirkin
2011-06-14 15:30 ` Hannes Reinecke
2011-06-29 10:00 ` Christoph Hellwig
2011-06-29 8:23 ` Paolo Bonzini
2011-06-29 8:46 ` Michael S. Tsirkin
2011-06-29 10:03 ` Christoph Hellwig
2011-06-29 10:06 ` Paolo Bonzini
2011-06-29 10:31 ` Michael S. Tsirkin
2011-06-29 10:35 ` Paolo Bonzini
2011-06-29 10:01 ` Christoph Hellwig
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=87lix9dioo.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=chellwig@redhat.com \
--cc=hare@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=virtualization@lists.linux-foundation.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).