From: Leon Alrae <leon.alrae@imgtec.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>, qemu-devel@nongnu.org
Cc: Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH RESEND] mips: Ensure PC update with MTC0 single-stepping
Date: Fri, 7 Nov 2014 10:42:39 +0000 [thread overview]
Message-ID: <545CA21F.2070207@imgtec.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1411060637400.2881@tp.orcam.me.uk>
On 06/11/2014 20:38, Maciej W. Rozycki wrote:
> Correct the way PC is updated when single-stepping instructions, by
> keeping the old PC only for the BS_EXCP (exception condition) state.
>
> Some MTC0 (and possibly other) instructions switch to the BS_STOP state
> to terminate the current translation block, so that the state transition
> of the simulated CPU resulting from the CP0 operation takes effect with
> the following instruction. This happens with `mtc0 <reg>,c0_config' for
> example, typically used to set KSEG0 cacheability.
>
> While single-stepping this has a side-effect of not advancing the PC
> past the instruction just executed; subsequent single-step traps will
> stop at the same instruction repeatedly. Example:
>
> (gdb) stepi
> 0x80004d24 in _start ()
> 5: x/i $pc
> => 0x80004d24 <_start+364>: mfc0 t1,c0_config
> (gdb)
> 0x80004d28 in _start ()
> 5: x/i $pc
> => 0x80004d28 <_start+368>: li at,-8
> (gdb)
> 0x80004d2c in _start ()
> 5: x/i $pc
> => 0x80004d2c <_start+372>: and t1,t1,at
> (gdb)
> 0x80004d30 in _start ()
> 5: x/i $pc
> => 0x80004d30 <_start+376>: ori t1,t1,0x3
> (gdb)
> 0x80004d34 in _start ()
> 5: x/i $pc
> => 0x80004d34 <_start+380>: mtc0 t1,c0_config
> (gdb)
> 0x80004d34 in _start ()
> 5: x/i $pc
> => 0x80004d34 <_start+380>: mtc0 t1,c0_config
> (gdb)
> 0x80004d34 in _start ()
> 5: x/i $pc
> => 0x80004d34 <_start+380>: mtc0 t1,c0_config
> (gdb)
> 0x80004d34 in _start ()
> 5: x/i $pc
> => 0x80004d34 <_start+380>: mtc0 t1,c0_config
> (gdb)
>
> -- oops!
>
> Signed-off-by: Maciej W. Rozycki <macro@codesourcery.com>
> ---
> It's been lost and waited for too long now, the original submission has
> been archived here:
>
> http://lists.gnu.org/archive/html/qemu-devel/2012-06/msg01227.html
>
> I have verified with a manual check that the issue is still there and
> that the fix still works. Please apply.
>
> Maciej
>
> qemu-mips-mtc0-step.diff
> Index: qemu-git-trunk/target-mips/translate.c
> ===================================================================
> --- qemu-git-trunk.orig/target-mips/translate.c 2014-11-02 18:51:10.838947420 +0000
> +++ qemu-git-trunk/target-mips/translate.c 2014-11-02 18:51:14.838939198 +0000
> @@ -17522,7 +17522,7 @@ gen_intermediate_code_internal(MIPSCPU *
> gen_io_end();
> }
> if (cs->singlestep_enabled && ctx.bstate != BS_BRANCH) {
> - save_cpu_state(&ctx, ctx.bstate == BS_NONE);
> + save_cpu_state(&ctx, ctx.bstate != BS_EXCP);
> gen_helper_0e0i(raise_exception, EXCP_DEBUG);
> } else {
> switch (ctx.bstate) {
>
Good fix for 2.2, thanks.
Reviewed-by: Leon Alrae <leon.alrae@imgtec.com>
Regards,
Leon
prev parent reply other threads:[~2014-11-07 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 1:05 [Qemu-devel] [PATCH] MIPS/system: MTC0 single-stepping PC update fix Maciej W. Rozycki
2012-06-12 14:32 ` Richard Henderson
2014-11-06 20:38 ` [Qemu-devel] [PATCH RESEND] mips: Ensure PC update with MTC0 single-stepping Maciej W. Rozycki
2014-11-07 10:42 ` Leon Alrae [this message]
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=545CA21F.2070207@imgtec.com \
--to=leon.alrae@imgtec.com \
--cc=aurelien@aurel32.net \
--cc=macro@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.