qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jun Koi <junkoi2004@gmail.com>
To: qemu-devel@nongnu.org, Jan Kiszka <jan.kiszka@siemens.com>
Subject: [Qemu-devel] [PATCH] flush TB on singlestep command
Date: Fri, 16 Apr 2010 10:03:44 +0900	[thread overview]
Message-ID: <o2hfdaac4d51004151803j9d1069d2nd9dfe3297bb64439@mail.gmail.com> (raw)

(Thanks to Jan for comments on the last patch)

Qemu has a command named singlestep, which reduces the translated code
block to be only one instruction.
However, there is one flaw when this command is triggered via monitor
interface: we do not flush all the current TBs, so we will miss
single-step on already translated code.
This patch fixes the problem by flushing all the TB to force new code
generation.

Signed-off-by: Jun Koi <junkoi2004@gmail.com>



diff --git a/monitor.c b/monitor.c
index 5659991..948b861 100644
--- a/monitor.c
+++ b/monitor.c
@@ -1190,8 +1190,14 @@ static void do_log(Monitor *mon, const QDict *qdict)
 static void do_singlestep(Monitor *mon, const QDict *qdict)
 {
     const char *option = qdict_get_try_str(qdict, "option");
+    CPUState *env;
+
     if (!option || !strcmp(option, "on")) {
         singlestep = 1;
+        /* flush all the TBs to force new code generation */
+        for (env = first_cpu; env != NULL; env = env->next_cpu) {
+            tb_flush(env);
+        }
     } else if (!strcmp(option, "off")) {
         singlestep = 0;
     } else {

             reply	other threads:[~2010-04-16  1:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16  1:03 Jun Koi [this message]
2010-04-16 21:13 ` [Qemu-devel] [PATCH] flush TB on singlestep command Stefan Weil
2010-04-20  1:17   ` Jun Koi
2010-04-20  7:18     ` [Qemu-devel] " Jan Kiszka
2010-04-20 10:51       ` Alexander Graf
2010-04-20 11:38         ` Jan Kiszka
2010-04-20 11:44           ` Alexander Graf
2010-04-21 10:04             ` Jun Koi
2010-04-21 10:11               ` Alexander Graf
2010-04-21 10:43                 ` Jan Kiszka
2010-04-21 19:20                   ` Stefan Weil
2010-04-22  7:02                     ` Jan Kiszka
2010-04-27 19:55                       ` Stefan Weil
2010-04-27 23:50                         ` Jun Koi
2010-04-28 18:06                           ` Stefan Weil
2010-04-22  7:14                     ` Jun Koi

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=o2hfdaac4d51004151803j9d1069d2nd9dfe3297bb64439@mail.gmail.com \
    --to=junkoi2004@gmail.com \
    --cc=jan.kiszka@siemens.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).