qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Avishay Traeger <AVISHAY@il.ibm.com>,
	kvm@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Jason Wang <jasowang@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	virtualization@lists.linux-foundation.org,
	Avi Kivity <avi@redhat.com>, Adam Litke <agl@us.ibm.com>,
	Amit Shah <amit.shah@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Sasha Levin <levinsasha928@gmail.com>
Subject: Re: [Qemu-devel] Proposal for virtio standardization.
Date: Tue, 9 Oct 2012 16:02:01 +0200	[thread overview]
Message-ID: <20121009160201.5303a7ca@BR9GNB5Z> (raw)
In-Reply-To: <87zk4c2tqq.fsf@rustcorp.com.au>

On Thu, 27 Sep 2012 09:59:33 +0930
Rusty Russell <rusty@rustcorp.com.au> wrote:

> Hi all,
> 
> 	I've had several requests for a more formal approach to the
> virtio draft spec, and (after some soul-searching) I'd like to try that.
> 
> 	The proposal is to use OASIS as the standards body, as it's
> fairly light-weight as these things go.  For me this means paperwork and
> setting up a Working Group and getting the right people involved as
> Voting members starting with the current contributors; for most of you
> it just means a new mailing list, though I'll be cross-posting any
> drafts and major changes here anyway.
> 
> 	I believe that a documented standard (aka virtio 1.0) will
> increase visibility and adoption in areas outside our normal linux/kvm
> universe.  There's been some of that already, but this is the clearest
> path to accelerate it.  Not the easiest path, but I believe that a solid
> I/O standard is a Good Thing for everyone.
> 
> 	Yet I also want to decouple new and experimental development
> from the standards effort; running code comes first.  New feature bits
> and new device numbers should be reservable without requiring a full
> spec change.
> 
> So the essence of my proposal is:
> 1) I start a Working Group within OASIS where we can aim for virtio spec
>    1.0.
> 
> 2) The current spec is textually reordered so the core is clearly
>    bus-independent, with PCI, mmio, etc appendices.
> 
> 3) Various clarifications, formalizations and cleanups to the spec text,
>    and possibly elimination of old deprecated features.
> 
> 4) The only significant change to the spec is that we use PCI
>    capabilities, so we can have infinite feature bits.
>    (see
> http://lists.linuxfoundation.org/pipermail/virtualization/2011-December/019198.html)

"Infinite" only applies to virtio-pci, no?

> 
> 5) Changes to the ring layout and other such things are deferred to a
>    future virtio version; whether this is done within OASIS or
>    externally depends on how well this works for the 1.0 release.
> 
> Thoughts?
> Rusty.
> 

Sounds like a good idea. I'll be happy to review the spec with an eye
to virtio-ccw.

Cornelia

  parent reply	other threads:[~2012-10-09 14:02 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27  0:29 [Qemu-devel] Proposal for virtio standardization Rusty Russell
2012-10-04 18:49 ` Anthony Liguori
2012-10-08  2:21   ` [Qemu-devel] Using PCI config space to indicate config location Rusty Russell
2012-10-08 13:58     ` Anthony Liguori
2012-10-08 14:58       ` Gerd Hoffmann
2012-10-08 15:09         ` Anthony Liguori
2012-10-08 20:13           ` Gerd Hoffmann
2012-10-08 20:55             ` Anthony Liguori
2012-10-08 23:56               ` Rusty Russell
2012-10-09  1:51                 ` Anthony Liguori
2012-10-09  3:16                   ` Rusty Russell
2012-10-09 10:17                     ` Avi Kivity
2012-10-09 14:03                       ` Anthony Liguori
2012-10-09 13:56                     ` Anthony Liguori
2012-10-10  3:44                       ` Rusty Russell
2012-10-10 11:37                         ` Michael S. Tsirkin
2012-10-09 21:09                     ` Jamie Lokier
2012-10-10  3:44                       ` Rusty Russell
2012-10-11  0:08                         ` Rusty Russell
2012-10-09  6:33                   ` Gerd Hoffmann
2012-10-09 15:26                     ` Anthony Liguori
2012-10-09 20:24                       ` Gerd Hoffmann
2012-10-10  2:54                         ` Rusty Russell
2012-10-10 13:36                           ` Anthony Liguori
2012-10-10 13:41                             ` Michael S. Tsirkin
2012-10-11  0:43                               ` Rusty Russell
2012-10-10  8:34                 ` Michael S. Tsirkin
2012-10-10  8:30     ` Michael S. Tsirkin
2012-10-11  1:18       ` Rusty Russell
2012-10-11 10:23         ` Michael S. Tsirkin
2012-10-11 22:29           ` Rusty Russell
2012-10-12  9:33             ` Michael S. Tsirkin
2012-10-12  9:51               ` Rusty Russell
2012-10-12 10:02                 ` Michael S. Tsirkin
2012-10-16 13:15                   ` Rusty Russell
2012-10-16 13:30                     ` Michael S. Tsirkin
2012-10-16 13:52                       ` Rusty Russell
2012-10-09 14:02 ` Cornelia Huck [this message]
2012-10-10  3:46   ` [Qemu-devel] Proposal for virtio standardization Rusty Russell

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=20121009160201.5303a7ca@BR9GNB5Z \
    --to=cornelia.huck@de.ibm.com \
    --cc=AVISHAY@il.ibm.com \
    --cc=agl@us.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=amit.shah@redhat.com \
    --cc=avi@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=ohad@wizery.com \
    --cc=pawel.moll@arm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    --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).