From: Frederic Konrad <fred.konrad@greensocs.com>
To: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, zealot351@gmail.com,
maria.klimushenkova@ispras.ru, mark.burton@greensocs.com,
batuzovk@ispras.ru
Subject: Re: [Qemu-devel] [PATCH] i386: fix breakpoints handling in icount mode
Date: Wed, 22 Oct 2014 14:53:15 +0200 [thread overview]
Message-ID: <5447A8BB.1060707@greensocs.com> (raw)
In-Reply-To: <20141022113831.9548.36452.stgit@PASHA-ISP>
On 22/10/2014 13:38, Pavel Dovgalyuk wrote:
Hi Pavel,
> This patch fixes instructions counting when execution is stopped on
> breakpoint (e.g. set from gdb). Without a patch extra instruction is translated
> and icount is incremented by invalid value (which equals to number of
> executed instructions + 1).
>
> Signed-off-by: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
> ---
> target-i386/translate.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/target-i386/translate.c b/target-i386/translate.c
> index 1284173..193cf9f 100644
> --- a/target-i386/translate.c
> +++ b/target-i386/translate.c
> @@ -8000,7 +8000,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);
> - break;
> + goto done_generating;
This makes sense to me.
But I don't see why you don't just "break" like the other instruction in
this loop?
> }
> }
> }
> @@ -8049,6 +8049,7 @@ static inline void gen_intermediate_code_internal(X86CPU *cpu,
> break;
> }
> }
> +done_generating:
> if (tb->cflags & CF_LAST_IO)
> gen_io_end();
Is there any reason why you don't jump over this two lines in case of a
breakpoint?
> gen_tb_end(tb, num_insns);
>
>
I'll give it a try later and I'll let you know.
Thanks,
Fred
next prev parent reply other threads:[~2014-10-22 12:53 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 [this message]
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
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=5447A8BB.1060707@greensocs.com \
--to=fred.konrad@greensocs.com \
--cc=Pavel.Dovgaluk@ispras.ru \
--cc=batuzovk@ispras.ru \
--cc=maria.klimushenkova@ispras.ru \
--cc=mark.burton@greensocs.com \
--cc=pbonzini@redhat.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 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).