qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Emmanuel Blot" <emmanuel.blot@sifive.com>
To: qemu-devel@nongnu.org
Cc: Alistair Francis <Alistair.Francis@wdc.com>
Subject: [PATCH] target/riscv: fix exception index on instruction access fault
Date: Fri, 16 Apr 2021 16:17:11 +0200	[thread overview]
Message-ID: <FB9EA197-B018-4879-AB0F-922C2047A08B@sifive.com> (raw)
In-Reply-To: 20210415134128.32670-1-emmanuel.blot@sifive.com

When no MMU is used and the guest code attempts to fetch an instruction
from an invalid memory location, the exception index defaults to a data
load access fault, rather an instruction access fault.

Signed-off-by: Emmanuel Blot <emmanuel.blot@sifive.com>

---
  target/riscv/cpu_helper.c | 4 +++-
  1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/target/riscv/cpu_helper.c b/target/riscv/cpu_helper.c
index 21c54ef5613..4e107b1bd23 100644
--- a/target/riscv/cpu_helper.c
+++ b/target/riscv/cpu_helper.c
@@ -691,8 +691,10 @@ void riscv_cpu_do_transaction_failed(CPUState *cs, 
hwaddr physaddr,

      if (access_type == MMU_DATA_STORE) {
          cs->exception_index = RISCV_EXCP_STORE_AMO_ACCESS_FAULT;
-    } else {
+    } else if (access_type == MMU_DATA_LOAD) {
          cs->exception_index = RISCV_EXCP_LOAD_ACCESS_FAULT;
+    } else {
+        cs->exception_index = RISCV_EXCP_INST_ACCESS_FAULT;
      }

      env->badaddr = addr;
-- 
2.31.1


       reply	other threads:[~2021-04-16 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210415134128.32670-1-emmanuel.blot@sifive.com>
2021-04-16 14:17 ` Emmanuel Blot [this message]
2021-04-20  0:56   ` [PATCH] target/riscv: fix exception index on instruction access fault Alistair Francis
2021-04-20  3:06     ` Alistair Francis

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=FB9EA197-B018-4879-AB0F-922C2047A08B@sifive.com \
    --to=emmanuel.blot@sifive.com \
    --cc=Alistair.Francis@wdc.com \
    --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).