All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel <qemu-devel@nongnu.org>, Blue Swirl <blauwirbel@gmail.com>
Cc: Max Filippov <jcmvbkbc@gmail.com>, Avi Kivity <avi@redhat.com>,
	TeLeMan <geleman@gmail.com>
Subject: [Qemu-devel] [PATCH] TCG: Fix TB invalidation after breakpoint insertion/deletion
Date: Wed, 23 May 2012 23:34:34 -0300	[thread overview]
Message-ID: <4FBD9E3A.6080704@web.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

From: Jan Kiszka <jan.kiszka@siemens.com>

tb_invalidate_phys_addr has to called with the exact physical address of
the breakpoint we add/remove, not just the page's base address.
Otherwise we easily fail to flush the right TB.

Regression of 1e7855a558.

Reported-by: TeLeMan <geleman@gmail.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 exec.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/exec.c b/exec.c
index a0494c7..efa1345 100644
--- a/exec.c
+++ b/exec.c
@@ -1492,7 +1492,8 @@ void tb_invalidate_phys_addr(target_phys_addr_t addr)
 
 static void breakpoint_invalidate(CPUArchState *env, target_ulong pc)
 {
-    tb_invalidate_phys_addr(cpu_get_phys_page_debug(env, pc));
+    tb_invalidate_phys_addr(cpu_get_phys_page_debug(env, pc) +
+                            (pc & ~TARGET_PAGE_MASK));
 }
 #endif
 #endif /* TARGET_HAS_ICE */
-- 
1.7.3.4


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

             reply	other threads:[~2012-05-24  2:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  2:34 Jan Kiszka [this message]
2012-05-24  2:44 ` [Qemu-devel] [PATCH] TCG: Fix TB invalidation after breakpoint insertion/deletion Jan Kiszka
2012-05-24 10:51 ` Max Filippov
2012-05-24 11:25   ` Jan Kiszka
2012-05-24 12:08     ` Max Filippov
2012-05-24 12:16       ` Jan Kiszka
2012-05-24 12:42         ` Max Filippov
2012-05-24 13:26           ` Jan Kiszka
2012-05-24 14:11             ` Max Filippov
2012-05-24 14:21               ` Jan Kiszka
2012-05-24 14:29                 ` Max Filippov
2012-05-24 14:34                   ` Jan Kiszka
2012-05-24 14:26               ` Avi Kivity
2012-05-24 19:58                 ` Max Filippov
2012-05-28  9:34                   ` Avi Kivity
2012-05-28 11:54                     ` Max Filippov
2012-05-28 12:04                       ` Avi Kivity

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=4FBD9E3A.6080704@web.de \
    --to=jan.kiszka@web.de \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=geleman@gmail.com \
    --cc=jcmvbkbc@gmail.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.