From: Rusty Russell <rusty@rustcorp.com.au>
To: Christoph Hellwig <hch@lst.de>
Cc: Alexey Zaytsev <alexey.zaytsev@gmail.com>,
Christoph Hellwig <hch@lst.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Avishay Traeger <avishay@il.ibm.com>,
linux-kernel@vger.kernel.org, Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH] virtio_blk: add block topology support
Date: Mon, 01 Aug 2011 14:52:10 +0930 [thread overview]
Message-ID: <87pqkp3dvh.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20110731181905.GA14288@lst.de>
On Sun, 31 Jul 2011 20:19:05 +0200, Christoph Hellwig <hch@lst.de> wrote:
> On Sat, Jul 30, 2011 at 02:22:42PM +0930, Rusty Russell wrote:
> > > I guess you could just remove VIRTIO_BLK_F_SECTOR_MAX from the spec.
> > > Linux did not implement it, and virtualbox does not have virtio block
> > > support at all. Are there any other known users, who might have
> > > implemented the VIRTIO_BLK_F_SECTOR_MAX feature?
> >
> > Did qemu implement it? If not, we'll simply kill it, and pretend it
> > never happened...
>
> It was never added to either qemu or the kernel. It would really help
> if we had a copy of the spec in a readable format (that is plain text)
> in major implementations of virtio like qemu and the kernel.
That's a really good idea. I've prepared a patch which puts the latest
version in the kernel source (Documentation/virtio/virtio-spec.txt).
Thanks!
Rusty.
prev parent reply other threads:[~2011-08-01 23:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 19:01 [PATCH] virtio_blk: add block topology support Christoph Hellwig
2010-01-30 4:59 ` Rusty Russell
2010-01-30 20:19 ` Christoph Hellwig
2010-02-01 1:10 ` Rusty Russell
2011-07-14 23:36 ` Alexey Zaytsev
2011-07-21 7:53 ` Rusty Russell
2011-07-29 19:09 ` Alexey Zaytsev
2011-07-30 4:52 ` Rusty Russell
2011-07-31 18:19 ` Christoph Hellwig
2011-08-01 5:22 ` Rusty Russell [this message]
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=87pqkp3dvh.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=alexey.zaytsev@gmail.com \
--cc=avi@redhat.com \
--cc=avishay@il.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.