From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>,
Pavel Dovgaluk <Pavel.Dovgaluk@ispras.ru>,
qemu-devel@nongnu.org
Cc: batuzovk@ispras.ru, zealot351@gmail.com,
maria.klimushenkova@ispras.ru, mark.burton@greensocs.com,
fred.konrad@greensocs.com
Subject: Re: [Qemu-devel] [PATCH] i386: fix breakpoints handling in icount mode
Date: Tue, 26 May 2015 16:56:14 +0200 [thread overview]
Message-ID: <5564898E.9000801@redhat.com> (raw)
In-Reply-To: <5561E380.5010003@web.de>
On 24/05/2015 16:43, Jan Kiszka wrote:
> diff --git a/target-i386/translate.c b/target-i386/translate.c
> index 305ce50..57b607d 100644
> --- a/target-i386/translate.c
> +++ b/target-i386/translate.c
> @@ -8006,6 +8006,7 @@ static inline void gen_intermediate_code_internal(X86CPU *cpu,
> if (bp->pc == pc_ptr &&
> !((bp->flags & BP_CPU) && (tb->flags & HF_RF_MASK))) {
> gen_debug(dc, pc_ptr - dc->cs_base);
> + pc_ptr = disas_insn(env, dc, pc_ptr);
> goto done_generating;
> }
> }
>
> pc_ptr is used at the end of the function to calculate the tb size. I
> suspect that the difference prevents that the breakpoint event is
> associated with the stored location. Can someone explain this more
> properly? Then I would happily pass patch credits.
So when a breakpoint is removed at address X, you have to also remove
translation blocks that end exactly at X? That is:
diff --git a/translate-all.c b/translate-all.c
index 536008f..6e50b8f 100644
--- a/translate-all.c
+++ b/translate-all.c
@@ -1113,7 +1116,7 @@
tb_start = tb->page_addr[1];
tb_end = tb_start + ((tb->pc + tb->size) & ~TARGET_PAGE_MASK);
}
- if (!(tb_end <= start || tb_start >= end)) {
+ if (tb_start < end && tb_end >= start) {
#ifdef TARGET_HAS_PRECISE_SMC
if (current_tb_not_found) {
current_tb_not_found = 0;
Does this fix the bug? Is there any other case where this
is desirable? Should tb_invalidate_phys_page_range grow another
argument to choose between "tb_end > start" and "tb_end >= start"?
Paolo
prev parent reply other threads:[~2015-05-26 14:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 11:38 [Qemu-devel] [PATCH] i386: fix breakpoints handling in icount mode Pavel Dovgalyuk
2014-10-22 12:53 ` Frederic Konrad
2014-10-23 5:57 ` Pavel Dovgaluk
2014-10-23 7:39 ` Frederic Konrad
2014-10-23 7:52 ` Pavel Dovgaluk
2014-10-23 8:47 ` Frederic Konrad
2014-10-23 9:58 ` Pavel Dovgaluk
2014-10-31 15:41 ` Paolo Bonzini
2015-01-12 8:03 ` Jan Kiszka
2015-01-12 8:26 ` Pavel Dovgaluk
2015-01-12 8:30 ` Jan Kiszka
2015-01-12 8:55 ` Paolo Bonzini
2015-05-24 14:43 ` Jan Kiszka
2015-05-26 14:56 ` Paolo Bonzini [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=5564898E.9000801@redhat.com \
--to=pbonzini@redhat.com \
--cc=Pavel.Dovgaluk@ispras.ru \
--cc=batuzovk@ispras.ru \
--cc=fred.konrad@greensocs.com \
--cc=jan.kiszka@web.de \
--cc=maria.klimushenkova@ispras.ru \
--cc=mark.burton@greensocs.com \
--cc=qemu-devel@nongnu.org \
--cc=zealot351@gmail.com \
/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.