From: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Liu Yu-B13201 <Yu.Liu-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kvm <kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RE: Virtio_pci in kernel ignore endian of PCI I/O space?
Date: Fri, 05 Sep 2008 10:30:50 -0500 [thread overview]
Message-ID: <1220628650.31152.4.camel@localhost.localdomain> (raw)
In-Reply-To: <C6FABC699EA2354EB260110329F4B3550D42B8-bKEhWGtIRUJ4Lp7cDGe+DVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
On Thu, 2008-09-04 at 13:27 +0800, Liu Yu-B13201 wrote:
> >
> > > Since E500 is big endian, this bring the misunderstanding
> > between qemu
> > > and guest.
> >
> > What are you using for PCI emulation in qemu? I don't think it should
> > matter in this case, since the kernel is doing 1-byte reads
> > in vp_get(),
> > but endianness gets very convoluted wherever qemu is involved. :(
> >
>
> Did you see Anthony's reply?
> It's weird that 440 can still work fine.
OK, I've found my problem. My host kernel is current, but my *guest*
kernel is old (it was still byte-swapping).
Also, the reason the S390 guys didn't see a problem is that they aren't
yet using qemu, and their virtio userspace implementation doesn't swap.
Yu, would you send a patch?
--
Hollis Blanchard
IBM Linux Technology Center
--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-09-05 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C6FABC699EA2354EB260110329F4B35508F638@zch01exm26.fsl.freescale.net>
2008-09-02 14:15 ` Virtio_pci in kernel ignore endian of PCI I/O space? Hollis Blanchard
[not found] ` <1220364956.26357.33.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-09-04 5:27 ` Liu Yu-B13201
[not found] ` <C6FABC699EA2354EB260110329F4B3550D42B8-bKEhWGtIRUJ4Lp7cDGe+DVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2008-09-05 15:30 ` Hollis Blanchard [this message]
[not found] ` <1220628650.31152.4.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-09-07 15:26 ` Liu Yu-B13201
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=1220628650.31152.4.camel@localhost.localdomain \
--to=hollisb-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=Yu.Liu-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.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