All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@stackframe.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, Sven Schnelle <svens@stackframe.org>,
	Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PATCH 10/11] target/hppa: exit TB if either Data or Instruction TLB changes
Date: Mon, 11 Mar 2019 20:16:01 +0100	[thread overview]
Message-ID: <20190311191602.25796-11-svens@stackframe.org> (raw)
In-Reply-To: <20190311191602.25796-1-svens@stackframe.org>

The current code assumes that we don't need to exit the TB
if a Data Cache Flush or Insert has happend. However, as we
have a shared Data/Instruction TLB, a Data cache flush also
flushes Instruction TLB entries, and a Data cache TLB insert
might also evict a Instruction TLB entry.

So exit the TB in all cases if Instruction translation is enabled.

Signed-off-by: Sven Schnelle <svens@stackframe.org>
---
 target/hppa/translate.c | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/target/hppa/translate.c b/target/hppa/translate.c
index a393a12252..fcacff963e 100644
--- a/target/hppa/translate.c
+++ b/target/hppa/translate.c
@@ -2474,9 +2474,8 @@ static bool trans_ixtlbx(DisasContext *ctx, arg_ixtlbx *a)
         gen_helper_itlbp(cpu_env, addr, reg);
     }
 
-    /* Exit TB for ITLB change if mmu is enabled.  This *should* not be
-       the case, since the OS TLB fill handler runs with mmu disabled.  */
-    if (!a->data && (ctx->tb_flags & PSW_C)) {
+    /* Exit TB for TLB change if mmu is enabled.  */
+    if (ctx->tb_flags & PSW_C) {
         ctx->base.is_jmp = DISAS_IAQ_N_STALE;
     }
     return nullify_end(ctx);
@@ -2503,7 +2502,7 @@ static bool trans_pxtlbx(DisasContext *ctx, arg_pxtlbx *a)
     }
 
     /* Exit TB for TLB change if mmu is enabled.  */
-    if (!a->data && (ctx->tb_flags & PSW_C)) {
+    if (ctx->tb_flags & PSW_C) {
         ctx->base.is_jmp = DISAS_IAQ_N_STALE;
     }
     return nullify_end(ctx);
-- 
2.20.1

  parent reply	other threads:[~2019-03-11 19:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 19:15 [Qemu-devel] [PATCH 00/11] target/hppa patches Sven Schnelle
2019-03-11 19:15 ` [Qemu-devel] [PATCH 01/11] target/hppa: fix overwriting source reg in addb Sven Schnelle
2019-03-12  3:24   ` Richard Henderson
2019-03-11 19:15 ` [Qemu-devel] [PATCH 02/11] target/hppa: fix TLB handling for page 0 Sven Schnelle
2019-03-12  3:24   ` Richard Henderson
2019-03-11 19:15 ` [Qemu-devel] [PATCH 03/11] target/hppa: report ITLB_EXCP_MISS for ITLB misses Sven Schnelle
2019-03-12  3:26   ` Richard Henderson
2019-03-11 19:15 ` [Qemu-devel] [PATCH 04/11] target/hppa: add TLB trace events Sven Schnelle
2019-03-12  3:26   ` Richard Henderson
2019-03-11 19:15 ` [Qemu-devel] [PATCH 05/11] target/hppa: remove PSW I/R/Q bit check Sven Schnelle
2019-03-12  3:26   ` Richard Henderson
2019-03-11 19:15 ` [Qemu-devel] [PATCH 06/11] target/hppa: ignore DIAG opcode Sven Schnelle
2019-03-12  0:22   ` Richard Henderson
2019-03-11 19:15 ` [Qemu-devel] [PATCH 07/11] target/hppa: fix b,gate instruction Sven Schnelle
2019-03-12  1:17   ` Richard Henderson
2019-03-11 19:15 ` [Qemu-devel] [PATCH 08/11] target/hppa: allow multiple itlbp without itlba Sven Schnelle
2019-03-12  1:22   ` Richard Henderson
2019-03-11 19:16 ` [Qemu-devel] [PATCH 09/11] target/hppa: add TLB protection id check Sven Schnelle
2019-03-12  3:23   ` Richard Henderson
2019-03-11 19:16 ` Sven Schnelle [this message]
2019-03-12  3:27   ` [Qemu-devel] [PATCH 10/11] target/hppa: exit TB if either Data or Instruction TLB changes Richard Henderson
2019-03-11 19:16 ` [Qemu-devel] [PATCH 11/11] target/hppa: call eval_interrupt() after ssm Sven Schnelle
2019-03-12  3:28   ` Richard Henderson
2019-03-12  4:01     ` Richard Henderson
2019-03-11 19:48 ` [Qemu-devel] [PATCH 00/11] target/hppa patches no-reply

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=20190311191602.25796-11-svens@stackframe.org \
    --to=svens@stackframe.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=rth@twiddle.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.