qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] [PATCH 2/8] irq: Introduce and use CPU_INTERRUPT_SSTEP_MASK.
Date: Sat, 30 Apr 2011 15:24:25 -0700	[thread overview]
Message-ID: <1304202271-24730-3-git-send-email-rth@twiddle.net> (raw)
In-Reply-To: <1304202271-24730-1-git-send-email-rth@twiddle.net>

This mask contains all of the bits that should be ignored while single
stepping in the debugger.  The mask contains 2 bits that are not currently
cleared, but are also never set.  The bits are included in the mask for
consistency in handling of the CPU_INTERRUPT_TGT_EXT_N bits.

Signed-off-by: Richard Henderson <rth@twiddle.net>
---
 cpu-all.h  |    8 ++++++++
 cpu-exec.c |    5 +----
 2 files changed, 9 insertions(+), 4 deletions(-)

diff --git a/cpu-all.h b/cpu-all.h
index 8c3222e..f813ef8 100644
--- a/cpu-all.h
+++ b/cpu-all.h
@@ -837,6 +837,14 @@ extern CPUState *cpu_single_env;
 #define CPU_INTERRUPT_SIPI	CPU_INTERRUPT_TGT_INT_2
 #define CPU_INTERRUPT_MCE	CPU_INTERRUPT_TGT_EXT_4
 
+/* The set of all bits that should be masked when single-stepping.  */
+#define CPU_INTERRUPT_SSTEP_MASK \
+    (CPU_INTERRUPT_HARD          \
+     | CPU_INTERRUPT_TGT_EXT_0   \
+     | CPU_INTERRUPT_TGT_EXT_1   \
+     | CPU_INTERRUPT_TGT_EXT_2   \
+     | CPU_INTERRUPT_TGT_EXT_3   \
+     | CPU_INTERRUPT_TGT_EXT_4)
 
 void cpu_interrupt(CPUState *s, int mask);
 void cpu_reset_interrupt(CPUState *env, int mask);
diff --git a/cpu-exec.c b/cpu-exec.c
index 395cd8c..5b42b25 100644
--- a/cpu-exec.c
+++ b/cpu-exec.c
@@ -360,10 +360,7 @@ int cpu_exec(CPUState *env1)
                 if (unlikely(interrupt_request)) {
                     if (unlikely(env->singlestep_enabled & SSTEP_NOIRQ)) {
                         /* Mask out external interrupts for this step. */
-                        interrupt_request &= ~(CPU_INTERRUPT_HARD |
-                                               CPU_INTERRUPT_FIQ |
-                                               CPU_INTERRUPT_SMI |
-                                               CPU_INTERRUPT_NMI);
+                        interrupt_request &= ~CPU_INTERRUPT_SSTEP_MASK;
                     }
                     if (interrupt_request & CPU_INTERRUPT_DEBUG) {
                         env->interrupt_request &= ~CPU_INTERRUPT_DEBUG;
-- 
1.7.4.4

  parent reply	other threads:[~2011-04-30 22:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30 22:24 [Qemu-devel] [PATCH 0/8] cpu interrupt cleanup Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 1/8] irq: Introduce CPU_INTERRUPT_TGT_* defines Richard Henderson
2011-04-30 22:24 ` Richard Henderson [this message]
2011-04-30 22:24 ` [Qemu-devel] [PATCH 3/8] target-mips: Do not check CPU_INTERRUPT_TIMER Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 4/8] target-sparc: " Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 5/8] irq: Remove CPU_INTERRUPT_TIMER Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 6/8] target-arm: Privatize CPU_INTERRUPT_FIQ Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 7/8] target-i386: Privatize some i386-specific interrupt names Richard Henderson
2011-04-30 22:24 ` [Qemu-devel] [PATCH 8/8] irq: Privatize CPU_INTERRUPT_NMI Richard Henderson
2011-04-30 22:36 ` [Qemu-devel] [PATCH 0/8] cpu interrupt cleanup Richard Henderson
2011-05-01  8:18   ` Jan Kiszka
2011-05-01 14:59     ` Richard Henderson
2011-05-01 17:31       ` Jan Kiszka
2011-05-04 19:19 ` Blue Swirl
  -- strict thread matches above, loose matches on Subject: below --
2011-05-04 20:34 [Qemu-devel] [PATCH 0/8] cpu interrupt cleanup, v2 Richard Henderson
2011-05-04 20:34 ` [Qemu-devel] [PATCH 2/8] irq: Introduce and use CPU_INTERRUPT_SSTEP_MASK Richard Henderson

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=1304202271-24730-3-git-send-email-rth@twiddle.net \
    --to=rth@twiddle.net \
    --cc=aurelien@aurel32.net \
    --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).