From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Pawel Moll <pawel.moll@arm.com>
Subject: Re: [Qemu-devel] [RFC 0/4] virtio-mmio transport
Date: Wed, 16 Nov 2011 18:41:40 +0000 [thread overview]
Message-ID: <CAFEAcA-aTc_hFZDfhfDtZ4Urg82Y7DKAnOLHoA_cp1L8st0U9A@mail.gmail.com> (raw)
In-Reply-To: <4EC3C9B1.5050109@redhat.com>
On 16 November 2011 14:33, Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 11/14/2011 03:55 PM, Peter Maydell wrote:
>>
>> This set of patches implements the QEMU end of the MMIO virtio transport
>> (as specified by Appendix X of the latest virtio spec from here
>> http://ozlabs.org/~rusty/virtio-spec/virtio.pdf
>> and implemented by patches which I think are going into Linux 3.2).
>
> How does this compare against hw/syborg_virtio.c?
Pawel may have more detail, but to me the significant difference
is that virtio-mmio is an implementation of a specification extension
agreed with the virtio spec maintainers, whereas syborg doesn't seem
to be mentioned in the virtio spec anywhere, so I am unsure what it
is intended to be implementing.
(There are some technical differences too, like virtio-mmio allowing
the guest to specify queue sizes and alignments; these mostly came
out of the process of agreeing the spec extension.)
-- PMM
next prev parent reply other threads:[~2011-11-16 18:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 14:55 [Qemu-devel] [RFC 0/4] virtio-mmio transport Peter Maydell
2011-11-14 14:55 ` [Qemu-devel] [RFC 1/4] virtio: Add support for guest setting of queue size Peter Maydell
2011-11-14 14:55 ` [Qemu-devel] [RFC 2/4] virtio: Support transports which can specify the vring alignment Peter Maydell
2011-11-14 14:55 ` [Qemu-devel] [RFC 3/4] Add MMIO based virtio transport Peter Maydell
2011-11-14 14:55 ` [Qemu-devel] [RFC 4/4] hw/vexpress.c: Add MMIO " Peter Maydell
2011-11-14 15:41 ` [Qemu-devel] [RFC 0/4] virtio-mmio transport Stefan Hajnoczi
2011-11-16 14:33 ` Paolo Bonzini
2011-11-16 18:41 ` Peter Maydell [this message]
2011-11-16 19:56 ` Anthony Liguori
2011-11-17 11:20 ` Pawel Moll
2011-11-17 11:44 ` Paolo Bonzini
2011-12-09 15:16 ` Paul Brook
2011-12-09 15:57 ` Anthony Liguori
2011-12-12 2:52 ` Paul Brook
2011-12-12 11:16 ` Pawel Moll
2011-12-12 14:45 ` Paul Brook
2011-12-12 14:51 ` Pawel Moll
2011-12-16 5:36 ` Rusty Russell
2011-12-12 12:14 ` Stefan Hajnoczi
2011-12-12 12:28 ` Pawel Moll
2011-12-12 13:12 ` Michael S. Tsirkin
2011-12-12 13:19 ` Pawel Moll
2011-12-12 15:11 ` Stefan Hajnoczi
2011-12-12 15:18 ` Peter Maydell
2011-12-12 15:21 ` Pawel Moll
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=CAFEAcA-aTc_hFZDfhfDtZ4Urg82Y7DKAnOLHoA_cp1L8st0U9A@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=pawel.moll@arm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).