From: Rusty Russell <rusty@rustcorp.com.au>
To: virtualization@lists.linux-foundation.org
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
Mark McLoughlin <markmc@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Christoph Hellwig <hch@lst.de>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: [RFC] virtio_pci draft spec
Date: Wed, 10 Jun 2009 13:17:13 +0930 [thread overview]
Message-ID: <200906101317.13744.rusty@rustcorp.com.au> (raw)
Hi all,
http://ozlabs.org/~rusty/virtio-spec/
I've been working on a draft spec for virtio PCI. It also serves (via the
appendices) as a spec for the various devices we have.
It's not entirely uptodate with latest changes, but it's a start.
Commentry and patches welcome (against the lyx source pref.)
Thanks,
Rusty.
next reply other threads:[~2009-06-10 3:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 3:47 Rusty Russell [this message]
2009-06-19 7:37 ` [RFC] virtio_pci draft spec Christian Bornträger
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=200906101317.13744.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=aliguori@us.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=hch@lst.de \
--cc=kvm-devel@lists.sourceforge.net \
--cc=markmc@redhat.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).