From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] target-alpha PALcode improvements
Date: Tue, 9 Jun 2015 14:12:30 -0700 [thread overview]
Message-ID: <1433884354-2550-1-git-send-email-rth@twiddle.net> (raw)
Rather than copying around a block of 8 registers when we swap modes,
let the translator map code generated for PALmode to the shadow regs
directly. This simplifies PALmode entry and exit sufficiently to
allow these insns to be performed inline.
Sadly, the speedup for this is in the noise. But I still think it
makes sense.
r~
Richard Henderson (3):
target-alpha: Use separate TCGv temporaries for the shadow registers
target-alpha: Inline call_pal
target-alpha: Inline hw_ret
target-alpha/cpu.h | 3 +-
target-alpha/gdbstub.c | 4 +-
target-alpha/helper.c | 63 ++++++---------
target-alpha/helper.h | 3 -
target-alpha/machine.c | 4 +-
target-alpha/sys_helper.c | 22 -----
target-alpha/translate.c | 201 ++++++++++++++++++++++++++++++----------------
7 files changed, 166 insertions(+), 134 deletions(-)
--
2.1.0
next reply other threads:[~2015-06-09 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 21:12 Richard Henderson [this message]
2015-06-09 21:12 ` [Qemu-devel] [PATCH 1/3] target-alpha: Use separate TCGv temporaries for the shadow registers Richard Henderson
2015-06-09 21:12 ` [Qemu-devel] [PATCH] tcg: Mask TCGMemOp appropriately for indexing Richard Henderson
2015-06-09 21:12 ` [Qemu-devel] [PATCH 2/3] target-alpha: Inline call_pal Richard Henderson
2015-06-09 21:12 ` [Qemu-devel] [PATCH 3/3] target-alpha: Inline hw_ret Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2015-06-09 21:13 [Qemu-devel] [PATCH 0/3] target-alpha PALcode improvements Richard Henderson
2015-06-12 22:12 ` Aurelien Jarno
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=1433884354-2550-1-git-send-email-rth@twiddle.net \
--to=rth@twiddle.net \
--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).