qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	jcmvbkbc@gmail.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 3/7] target-xtensa: raise an exception for invalid and reserved opcodes
Date: Tue,  1 Nov 2011 02:17:30 +0400	[thread overview]
Message-ID: <1320099455-17326-6-git-send-email-jcmvbkbc@gmail.com> (raw)
In-Reply-To: <1320099455-17326-1-git-send-email-jcmvbkbc@gmail.com>

This includes opcodes from disabled features and those marked reserved in the ISA.
Also end TB on opcodes that definitely generate an exception: illegal
instructions, syscall and privileged instructions.

Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
---
 target-xtensa/translate.c |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)

diff --git a/target-xtensa/translate.c b/target-xtensa/translate.c
index b724d46..c81450d 100644
--- a/target-xtensa/translate.c
+++ b/target-xtensa/translate.c
@@ -266,6 +266,10 @@ static void gen_exception_cause(DisasContext *dc, uint32_t cause)
     gen_helper_exception_cause(tpc, tcause);
     tcg_temp_free(tpc);
     tcg_temp_free(tcause);
+    if (cause == ILLEGAL_INSTRUCTION_CAUSE ||
+            cause == SYSCALL_CAUSE) {
+        dc->is_jmp = DISAS_UPDATE;
+    }
 }
 
 static void gen_exception_cause_vaddr(DisasContext *dc, uint32_t cause,
@@ -283,6 +287,7 @@ static void gen_check_privilege(DisasContext *dc)
 {
     if (dc->cring) {
         gen_exception_cause(dc, PRIVILEGED_CAUSE);
+        dc->is_jmp = DISAS_UPDATE;
     }
 }
 
@@ -2378,7 +2383,7 @@ static void disas_xtensa_insn(DisasContext *dc)
 
 invalid_opcode:
     qemu_log("INVALID(pc = %08x)\n", dc->pc);
-    dc->pc = dc->next_pc;
+    gen_exception_cause(dc, ILLEGAL_INSTRUCTION_CAUSE);
 #undef HAS_OPTION
 }
 
-- 
1.7.6.4

  parent reply	other threads:[~2011-10-31 22:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 22:17 [Qemu-devel] [PULL 0/7] target-xtensa patches for 1.0 Max Filippov
2011-10-31 22:17 ` [Qemu-devel] [PATCH 1/7] target-xtensa: mask out undefined bits of WINDOWBASE SR Max Filippov
2011-11-02 13:34   ` [Qemu-devel] [PATCH v2] target-xtensa: mask out undefined bits of WINDOWSTART SR Max Filippov
2011-10-31 22:17 ` [Qemu-devel] [PATCH 1/3] xtensa_lx60: add FLASH support Max Filippov
2011-10-31 22:17 ` [Qemu-devel] [PATCH 2/7] target-xtensa: handle cache options in the overlay tool Max Filippov
2011-10-31 22:17 ` [Qemu-devel] [PATCH 2/3] xtensa_lx60: pass kernel arguments from -append Max Filippov
2011-10-31 22:17 ` Max Filippov [this message]
2011-10-31 22:17 ` [Qemu-devel] [PATCH 3/3] xtensa_lx60: fix build date code and change memory region names Max Filippov
2011-10-31 22:17 ` [Qemu-devel] [PATCH 4/7] opencores_eth: fix RX path: FCS, padding and TL Max Filippov
2011-10-31 22:17 ` [Qemu-devel] [PATCH 5/7] xtensa_lx60: add FLASH support Max Filippov
2011-10-31 22:17 ` [Qemu-devel] [PATCH 6/7] xtensa_lx60: pass kernel arguments from -append Max Filippov
2011-10-31 22:17 ` [Qemu-devel] [PATCH 7/7] xtensa_lx60: fix build date code and change memory region names Max Filippov
2011-10-31 22:26 ` [Qemu-devel] [PULL 0/7] target-xtensa patches for 1.0 Max Filippov
2011-11-02 20:55 ` Blue Swirl

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=1320099455-17326-6-git-send-email-jcmvbkbc@gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.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).