qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: "J. Mayer" <l_indien@magic.fr>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: reverse-endian softmmu memory accessors
Date: Sun, 14 Oct 2007 14:22:06 +0100	[thread overview]
Message-ID: <20071014132206.GR3379@networkno.de> (raw)
In-Reply-To: <1192356863.9976.374.camel@rapid>

J. Mayer wrote:
[snip]
> > > Here's a new version. The only change is that, for consistency, I did
> > > add the big-endian and little-endian accessors that were documented in
> > > cpu-all.h as unimplemented. The implementation is quite trivial, having
> > > native and reverse-endian accessors available, and changes functionnally
> > > nothing to the previous version.
> > 
> > The patch does not apply anymore. The Sparc part looks OK.
> > 
> > The benefits from the patch can be gained by mapping Sparc64 lduw and
> > ldsw in op_mem.h  directly to ldul and ldsl using SPARC_LD_OP and
> > replacing the ldl+bswap etc. for the LE cases with ldlr in
> > op_helper.c. If you prefer, I can do this after you have applied the
> > patch.
> 
> Yes, there are conflicts between this patch and the mmu_idx one I just
> commited. I will regenerate an updated diff in the hours to come, after
> I finished commiting the PowerPC fixes and improvments I got waiting in
> stock.
> For the Sparc improvments, as I merged the PowerPC improvments in the
> patch, I think it can be a good idea to include it directly in the
> patch.
> I'm also wondering if it would not be a good idea to define lduq/ldsq
> even if they in fact do exactly what ldq does now, just to have a fully
> consistent API.

Some architecture specs mention the possibility of 128 bit integers, so
this sounds like a good idea.


Thiemo

  reply	other threads:[~2007-10-14 13:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-13  9:56 [Qemu-devel] RFC: reverse-endian softmmu memory accessors 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 [this message]
2007-10-15 11:55                 ` J. Mayer
2007-10-13 13:02   ` Thiemo Seufer
  -- strict thread matches above, loose matches on Subject: below --
2007-10-14 11:49 J. Mayer
2007-10-14 12:59 ` Blue Swirl
2007-10-15 12:10   ` J. Mayer
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

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=20071014132206.GR3379@networkno.de \
    --to=ths@networkno.de \
    --cc=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).