From: Richard Henderson <rth@twiddle.net>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [RFC] Streamlining endian handling in TCG
Date: Wed, 28 Aug 2013 14:23:02 -0700 [thread overview]
Message-ID: <521E6A36.8050602@twiddle.net> (raw)
In-Reply-To: <20130828204239.GA11047@smtp.vpn>
On 08/28/2013 01:42 PM, Edgar E. Iglesias wrote:
> A question, some archs have an endian swap
> controlled via the MMU, e.g per page selectable (some PPC, microblaze and
> maybe others). AFAIK the behaviour is implementable in QEMU today but not
> very efficiently. Any thoughts/ideas on this?
The only thing I could imagine doing on a page-by-page basis like
this is to bring this feature into the qemu page table.
We'd have to hang it under the same general scheme as an IO access,
where all reads/writes to the page are forced through the helper.
I'd imagine that it would get handled similarly to io_mem_rom, but
with different accessors.
r~
next prev parent reply other threads:[~2013-08-28 21:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 4:39 [Qemu-devel] [PATCH] target-arm: Report unimplemented opcodes (LOG_UNIMP) Stefan Weil
2013-08-28 8:15 ` Peter Maydell
2013-08-28 14:31 ` Richard Henderson
2013-08-28 14:34 ` Peter Maydell
2013-08-28 15:26 ` [Qemu-devel] [RFC] Streamlining endian handling in TCG Richard Henderson
2013-08-28 16:38 ` Peter Maydell
2013-08-28 17:16 ` Richard Henderson
2013-08-28 17:28 ` Peter Maydell
2013-08-28 17:45 ` Richard Henderson
2013-08-28 17:41 ` Stefan Weil
2013-08-28 20:42 ` Edgar E. Iglesias
2013-08-28 21:06 ` Peter Maydell
2013-08-28 21:23 ` Richard Henderson [this message]
2013-09-02 23:42 ` Aurelien Jarno
2013-09-03 15:11 ` Richard Henderson
2013-09-01 15:35 ` [Qemu-devel] [Qemu-trivial] [PATCH] target-arm: Report unimplemented opcodes (LOG_UNIMP) Michael Tokarev
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=521E6A36.8050602@twiddle.net \
--to=rth@twiddle.net \
--cc=aurelien@aurel32.net \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--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).