qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Zuepke <azuepke@sysgo.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] ARM: BKPT instructions should raise prefetch aborts with IFSR type 00010
Date: Fri, 25 Mar 2011 11:54:23 +0100	[thread overview]
Message-ID: <4D8C745F.2000304@sysgo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 362 bytes --]

Hi,

while digging through some problems with BKPT exceptions on ARM, I
discovered that QEMU does not update IFSR on prefetch aborts. This
should be done since ARMv6 according to ARM docs. Please include.

Best Regards,
Alex

-- 
Alexander Zuepke                                azuepke@sysgo.com
SYSGO AG ~ Am Pfaffenstein 14 ~ 55270 Klein-Winternheim ~ Germany

[-- Attachment #2: qemu_arm_bkpt_ifsr_update.patch --]
[-- Type: text/x-diff, Size: 734 bytes --]

 target-arm: BKPT instructions should raise prefetch aborts with IFSR type 00010
 diff against qemu 0.14.0
 Signed-off-by: Alex Zuepke <azuepke@sysgo.com>
--- qemu-0.14.0.orig/target-arm/translate.c	2011-02-16 15:44:05.000000000 +0100
+++ qemu-0.14.0/target-arm/translate.c	2011-03-25 11:22:03.000000000 +0100
@@ -6389,6 +6389,7 @@
                 goto illegal_op;
             }
             /* bkpt */
+            env->cp15.c5_insn = 2;
             gen_exception_insn(s, 4, EXCP_BKPT);
             break;
         case 0x8: /* signed multiply */
@@ -8930,6 +8931,7 @@
             break;
 
         case 0xe: /* bkpt */
+            env->cp15.c5_insn = 2;
             gen_exception_insn(s, 2, EXCP_BKPT);
             break;
 

             reply	other threads:[~2011-03-25 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 10:54 Alex Zuepke [this message]
2011-03-25 11:39 ` [Qemu-devel] ARM: BKPT instructions should raise prefetch aborts with IFSR type 00010 Peter Maydell
2011-03-25 14:01   ` Alex Zuepke
2011-05-18 10:00   ` Alex Zuepke
2011-05-18 17:44     ` Peter Maydell
2011-06-03 16:42     ` 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=4D8C745F.2000304@sysgo.com \
    --to=azuepke@sysgo.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).