From: Jun Koi <junkoi2004@gmail.com>
To: takasi-y@ops.dti.ne.jp
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Missing singlestep for already-translated code?
Date: Tue, 13 Apr 2010 18:48:40 +0900 [thread overview]
Message-ID: <z2kfdaac4d51004130248we1949f2br518a58d93dcdfcd7@mail.gmail.com> (raw)
In-Reply-To: <20100413182130.e8ae2da6.takasi-y@ops.dti.ne.jp>
On Tue, Apr 13, 2010 at 6:21 PM, <takasi-y@ops.dti.ne.jp> wrote:
> Hi,
>> So for the already-translated code, we will miss singlestep?
> At least SH4(and mips?) shows such behaviour.
> I think a patch below enables single stepping in such case, too.
> But, I'm not sure if this behaviour is on purpose, nor this patch is correct.
> /yoshii
>
> diff --git a/target-sh4/translate.c b/target-sh4/translate.c
> index 3537f8c..dfa724a 100644
> --- a/target-sh4/translate.c
> +++ b/target-sh4/translate.c
> @@ -300,7 +300,7 @@ static void gen_goto_tb(DisasContext * ctx, int n, target_ulong dest)
> tb = ctx->tb;
>
> if ((tb->pc & TARGET_PAGE_MASK) == (dest & TARGET_PAGE_MASK) &&
> - !ctx->singlestep_enabled) {
> + !ctx->singlestep_enabled && !singlestep) {
> /* Use a direct jump if in same page and singlestep not enabled */
> tcg_gen_goto_tb(n);
> tcg_gen_movi_i32(cpu_pc, dest);
>
The first glance: because you are patching translate.c, I dont think
you fixed the problem.
Thanks,
J
next prev parent reply other threads:[~2010-04-13 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 4:03 [Qemu-devel] Missing singlestep for already-translated code? Jun Koi
2010-04-13 9:21 ` [Qemu-devel] " takasi-y
2010-04-13 9:48 ` Jun Koi [this message]
2010-04-13 13:36 ` Jan Kiszka
2010-04-13 14:10 ` Alexander Graf
2010-04-13 15:28 ` Jan Kiszka
2010-04-15 4:10 ` Jun Koi
2010-04-15 8:59 ` Jan Kiszka
2010-04-15 10:02 ` Aurelien Jarno
2010-04-15 10:13 ` Jan Kiszka
2010-04-15 11:41 ` 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=z2kfdaac4d51004130248we1949f2br518a58d93dcdfcd7@mail.gmail.com \
--to=junkoi2004@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=takasi-y@ops.dti.ne.jp \
/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).