qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jincheng Miao <jmiao@redhat.com>
To: qemu-devel@nongnu.org
Cc: riku.voipio@iki.fi, Jincheng Miao <jmiao@redhat.com>, rth@twiddle.net
Subject: [Qemu-devel] [PATCH] cpu-exec: make TBs generated codes unlinked when -singlestep
Date: Fri, 25 Jul 2014 12:37:53 +0800	[thread overview]
Message-ID: <1406263073-635-1-git-send-email-jmiao@redhat.com> (raw)

'-singlestep' option will make TB contains only one instruction,
so that the qemu_log could output trace log when CPU_LOG_EXEC sets,
and it could help developers to debug control flow.

But currently, in cpu_exec(), it doesn't check singlestep when
tb_add_jump(), so the TB linked is executed siliently.
Therefore, this patch adds singlestep check before tb_add_jump().

Signed-off-by: Jincheng Miao <jmiao@redhat.com>
---
 cpu-exec.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/cpu-exec.c b/cpu-exec.c
index 38e5f02..64b7289 100644
--- a/cpu-exec.c
+++ b/cpu-exec.c
@@ -622,8 +622,8 @@ int cpu_exec(CPUArchState *env)
                 }
                 /* see if we can patch the calling TB. When the TB
                    spans two pages, we cannot safely do a direct
-                   jump. */
-                if (next_tb != 0 && tb->page_addr[1] == -1) {
+                   jump. So as when singlestep is enabled. */
+                if (next_tb != 0 && tb->page_addr[1] == -1 && !singlestep) {
                     tb_add_jump((TranslationBlock *)(next_tb & ~TB_EXIT_MASK),
                                 next_tb & TB_EXIT_MASK, tb);
                 }
-- 
1.7.1

             reply	other threads:[~2014-07-25  4:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25  4:37 Jincheng Miao [this message]
2014-07-25  6:58 ` [Qemu-devel] [PATCH] cpu-exec: make TBs generated codes unlinked when -singlestep Richard Henderson
2014-07-25  7:37   ` Peter Maydell
2014-07-25  7:41     ` Richard Henderson
2014-07-25  7:45       ` Peter Maydell
2014-07-25  8:05         ` Jincheng Miao
2014-07-25 12:07 ` Laurent Desnogues

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=1406263073-635-1-git-send-email-jmiao@redhat.com \
    --to=jmiao@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=rth@twiddle.net \
    /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).