aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorpbrook <pbrook@c046a42c-6fe2-441c-8c8c-71466251a162>2008-10-22 16:14:08 +0000
committerpbrook <pbrook@c046a42c-6fe2-441c-8c8c-71466251a162>2008-10-22 16:14:08 +0000
commit4be27dbbde2aed1da305b83043caa6f0f0ca4309 (patch)
tree77aad647b51e997dca13a69511a47a369bbc5ffe
parent3a742b76431e3dd2ee046aa56317ad36a903db30 (diff)
Optimize redundant cp15 coprocessor access control register writes.
Signed-off-by: Paul Brook <paul@codesourcery.com> git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5512 c046a42c-6fe2-441c-8c8c-71466251a162
-rw-r--r--target-arm/helper.c8
1 files changed, 5 insertions, 3 deletions
diff --git a/target-arm/helper.c b/target-arm/helper.c
index b9a8f78b2c..d4af8595ca 100644
--- a/target-arm/helper.c
+++ b/target-arm/helper.c
@@ -1334,9 +1334,11 @@ void HELPER(set_cp15)(CPUState *env, uint32_t insn, uint32_t val)
case 2:
if (arm_feature(env, ARM_FEATURE_XSCALE))
goto bad_reg;
- env->cp15.c1_coproc = val;
- /* ??? Is this safe when called from within a TB? */
- tb_flush(env);
+ if (env->cp15.c1_coproc != val) {
+ env->cp15.c1_coproc = val;
+ /* ??? Is this safe when called from within a TB? */
+ tb_flush(env);
+ }
break;
default:
goto bad_reg;