All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: virtualization@lists.linux-foundation.org
Cc: Alexander Graf <agraf@suse.de>,
	"Ira W. Snyder" <iws@ovro.caltech.edu>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Zang Roy <r61911@freescale.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: Using virtio as a physical (wire-level) transport
Date: Mon, 16 Aug 2010 09:49:40 +0930	[thread overview]
Message-ID: <201008160949.41348.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4C336074-FC8C-4BDF-B945-5295133CDB38@suse.de>

On Sat, 14 Aug 2010 09:04:19 pm Alexander Graf wrote:
> 
> Am 06.08.2010 um 11:34 schrieb "Ira W. Snyder" <iws@ovro.caltech.edu>:
> > This problem is not limited to my new use of virtio. Virtio is
> > completely useless in a relatively common virtualization scenario:
> > x86 host with qemu-ppc guest. Or any other big endian guest system.
> 
> This one actually works because we know that we're building for a BE guest.
> But I agree that it's a mess and clearly a very incorrect design decision.

Yes, since you need to know the guest's endian to virtualize it, the
correct interpretation of the virtio ring seemed the least problem.  Perhaps
I went overboard in simplification here, but it seemed pure legacy.

If we did a virtio2, as has been suggested, it would be possible to address
this.  You could of course do a hack where you detect the ring endianness
the first time they use it (based on avail.flags, avail.index and the
descriptor it would be quite reliable in practice).

Cheers,
Rusty.

  parent reply	other threads:[~2010-08-16  0:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04 23:04 Using virtio as a physical (wire-level) transport Ira W. Snyder
2010-08-05 21:30 ` Michael S. Tsirkin
2010-08-05 21:30 ` Michael S. Tsirkin
2010-08-05 23:01   ` Ira W. Snyder
2010-08-05 23:20     ` Michael S. Tsirkin
2010-08-06 15:34       ` Ira W. Snyder
2010-08-06 15:34       ` Ira W. Snyder
2010-08-14 11:34         ` Alexander Graf
2010-08-16  0:19           ` Rusty Russell
2010-08-16  0:19           ` Rusty Russell [this message]
2010-09-06 11:19           ` Michael S. Tsirkin
2010-09-06 11:19           ` Michael S. Tsirkin
2010-08-14 11:34         ` Alexander Graf
2010-08-05 23:20     ` Michael S. Tsirkin
2010-08-05 23:01   ` Ira W. Snyder

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=201008160949.41348.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=agraf@suse.de \
    --cc=iws@ovro.caltech.edu \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=r61911@freescale.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 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.