qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marius Groeger <mgroeger@sysgo.com>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH][Qemu-devel] Single stepping for PPC broken!
Date: Thu, 10 Jan 2008 14:57:50 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0801101454460.20346@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0801091312170.24129@localhost>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1098 bytes --]

On Wed, 9 Jan 2008, Marius Groeger wrote:

> On Wed, 9 Jan 2008, Marius Groeger wrote:
> 
> > I'm having problems with qemu's (-M prep, -cpu 604) handling of the 
> > MSR_SE bit. My gdbstub can successfully step along regular code, but 
> > qemu chokes when stepping over a branch instruction like "blr". 
> > (Needless to say, that same gdbstub works fine on real hardware). I 
> > tried older versions of qemu and found that the code base 8 months ago 
> > worked fine.
> 
> I have now verified with booting a Linux image into qemu-system-ppc - same
> problem. When stepi'ing over the following sequence, the system chokes on a
> "bl" instruction:

The attached patch fixes the problem, but I have to admit I can't tell 
for sure if this doesn't break other things (such as qemu's built-in 
GDB server). Could some QEMU ppc expert please comment on this?

Thanks
Marius

-- 
Marius Groeger <mgroeger@sysgo.com>
SYSGO AG                      Embedded and Real-Time Software
Voice: +49 6136 9948 0                  FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.pikeos.com

[-- Attachment #2: Type: TEXT/PLAIN, Size: 987 bytes --]

Index: target-ppc/translate.c
===================================================================
RCS file: /sources/qemu/qemu/target-ppc/translate.c,v
retrieving revision 1.115
diff -u -r1.115 translate.c
--- target-ppc/translate.c	24 Nov 2007 02:03:55 -0000	1.115
+++ target-ppc/translate.c	10 Jan 2008 13:54:36 -0000
@@ -2811,8 +2811,6 @@
 #endif
             gen_op_b_T1();
         gen_op_set_T0((long)tb + n);
-        if (ctx->singlestep_enabled)
-            gen_op_debug();
         gen_op_exit_tb();
     } else {
         gen_set_T1(dest);
@@ -2823,8 +2821,6 @@
 #endif
             gen_op_b_T1();
         gen_op_reset_T0();
-        if (ctx->singlestep_enabled)
-            gen_op_debug();
         gen_op_exit_tb();
     }
 }
@@ -3007,8 +3003,6 @@
             gen_op_btest_T1(ctx->nip);
         gen_op_reset_T0();
     no_test:
-        if (ctx->singlestep_enabled)
-            gen_op_debug();
         gen_op_exit_tb();
     }
  out:

  reply	other threads:[~2008-01-10 13:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09  7:59 [Qemu-devel] Single stepping for PPC broken? Marius Groeger
2008-01-09 12:19 ` [Qemu-devel] Single stepping for PPC broken! Marius Groeger
2008-01-10 13:57   ` Marius Groeger [this message]
2008-02-11 23:22     ` [PATCH][Qemu-devel] " Rob Landley
2008-02-13  8:46       ` Marius Groeger
2008-02-13 13:44         ` Daniel Jacobowitz
2008-02-13 15:52           ` Marius Groeger
2008-02-13 16:19             ` Daniel Jacobowitz
2008-02-14  7:36               ` Marius Groeger
2008-03-11 23:16     ` Jason Wessel

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=Pine.LNX.4.64.0801101454460.20346@localhost \
    --to=mgroeger@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).