From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Wanted: A better way to implement MIPS unaligned instructions
Date: Tue, 17 Jun 2008 23:56:22 +0200 [thread overview]
Message-ID: <48583306.8090600@bellard.org> (raw)
In-Reply-To: <20080617121251.GB23435@networkno.de>
Thiemo Seufer wrote:
> Hello All,
>
> I am currently trying to implement TCG versions of the MIPS [ls][dw][lr]
> set of instructions. I believe I can't use a helper function for
> load/store type instructions. The appended patch uses TCG directly, but
> the resulting translation is excessively complicated. Is there a better
> way to do this?
A simpler solution is to use the same code as before in an helper.
Helpers are perfectly usable in this case provided the cpu state is
saved before calling them.
When the helper solution will work, it will be possible to optimize it
by directly accessing the QEMU TLB cache to do word accesses and to
generate the correct exception.
Fabrice.
prev parent reply other threads:[~2008-06-17 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 12:12 [Qemu-devel] Wanted: A better way to implement MIPS unaligned instructions Thiemo Seufer
2008-06-17 21:56 ` Fabrice Bellard [this message]
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=48583306.8090600@bellard.org \
--to=fabrice@bellard.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).