From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:50123) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQlbA-0006Rc-0B for qemu-devel@nongnu.org; Wed, 16 Nov 2011 14:56:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RQlb8-00009v-Dr for qemu-devel@nongnu.org; Wed, 16 Nov 2011 14:56:43 -0500 Received: from mail-yx0-f173.google.com ([209.85.213.173]:53123) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQlb8-00009S-BJ for qemu-devel@nongnu.org; Wed, 16 Nov 2011 14:56:42 -0500 Received: by yenq2 with SMTP id q2so112910yen.4 for ; Wed, 16 Nov 2011 11:56:40 -0800 (PST) Message-ID: <4EC41574.5080606@codemonkey.ws> Date: Wed, 16 Nov 2011 13:56:36 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <1321282528-19070-1-git-send-email-peter.maydell@linaro.org> <4EC3C9B1.5050109@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC 0/4] virtio-mmio transport List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Paolo Bonzini , qemu-devel , Pawel Moll , Paul Brook On 11/16/2011 12:41 PM, Peter Maydell wrote: > On 16 November 2011 14:33, Paolo Bonzini 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.) Correct. Syborg virtio was something Paul Brook did bit is not an "official" virtio transport as far as Linux or the spec is concerned. I'm not sure what guest software uses the syborg virtio transport. Regards, Anthony Liguori > > -- PMM >