From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: reverse-endian softmmu memory accessors
Date: Mon, 15 Oct 2007 14:10:33 +0200 [thread overview]
Message-ID: <1192450234.9976.413.camel@rapid> (raw)
In-Reply-To: <f43fc5580710140559y5861c095i14101be4340348cc@mail.gmail.com>
On Sun, 2007-10-14 at 15:59 +0300, Blue Swirl wrote:
> On 10/14/07, J. Mayer <l_indien@magic.fr> wrote:
> > Here's an updated version of the patch against current CVS.
> > This patches provides reverse-endian, little-endian and big-endian
> > memory accessors, available with and without softmmu. It also provides
> > an IO_MEM_REVERSE TLB flag to allow future support of per-page
> > endianness control, which is required by some targets CPU emulations.
> > Having reverse-endian memory accessors also make it possible to optimise
> > reverse-endian memory access when the target CPU has dedicated
> > instructions. For now, it includes optimisations for the PowerPC target.
>
> This breaks Sparc32 softmmu, I get a black screen. Your changes to
> target-sparc and hw/sun4m.c look fine, so the problem could be in IO?
Did it worked before my commits ? I may have done something wrong during
the merge...
I will do more checks and more tests...
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2007-10-15 12:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 11:49 [Qemu-devel] RFC: reverse-endian softmmu memory accessors J. Mayer
2007-10-14 12:59 ` Blue Swirl
2007-10-15 12:10 ` J. Mayer [this message]
2007-10-15 16:02 ` Blue Swirl
2007-10-15 17:45 ` Blue Swirl
2007-10-16 20:27 ` J. Mayer
2007-11-23 12:55 ` Tero Kaarlela
2007-10-15 21:06 ` J. Mayer
-- strict thread matches above, loose matches on Subject: below --
2007-10-13 9:56 J. Mayer
2007-10-13 10:47 ` Blue Swirl
2007-10-13 12:43 ` J. Mayer
2007-10-13 13:07 ` Blue Swirl
2007-10-13 14:17 ` J. Mayer
2007-10-13 22:07 ` J. Mayer
2007-10-13 22:53 ` Thiemo Seufer
2007-10-14 8:19 ` Blue Swirl
2007-10-14 10:14 ` J. Mayer
2007-10-14 13:22 ` Thiemo Seufer
2007-10-15 11:55 ` J. Mayer
2007-10-13 13:02 ` Thiemo Seufer
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=1192450234.9976.413.camel@rapid \
--to=l_indien@magic.fr \
--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).