From: Sergey Fedorov <serge.fdrv@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ARM softmmu breakpoint misbehavior
Date: Tue, 1 Sep 2015 14:58:21 +0300 [thread overview]
Message-ID: <55E592DD.2030302@gmail.com> (raw)
In-Reply-To: <CAFEAcA_U7ptfOVnbVGRfhCn2Jr+U3MK=YEsd6Jvp0ui6x6RC0w@mail.gmail.com>
28.08.2015 22:21, Peter Maydell wrote:
> I think what we need to do is have the translate-a64.c
> code be smarter, and actually generate the real code
> if we're not going to really hit the bp. Except that we
> don't really have all the info in the flags to know for
> sure about that. So we probably need to do something like
> generating a call to a helper which checks whether this
> bp should hit and doesn't throw the exception unless it
> has to, with the actual code for the insn following.
> I need to think about how this ought to work...
I think we should only generate a CPU breakpoint TCG exception when it
is really going to become a CPU exception (or a GDB exception). It could
be done by moving the logic of check_breakpoints() to a helper called
from TB.
> The watchpoint code has a chance of cpu_resume_from_signal
> doing the right thing, because we really did have the
> code to do the load/store. However I have a feeling this
> won't interact properly with the fact that ARM needs
> BP_STOP_BEFORE_ACCESS on its watchpoints (unlike x86, which
> is where I was looking at when I wrote the ARM wp handling
> code.) So we may well be broken there as well in the
> case where check_watchpoints() returns false.
As of watchpoints, I'm going to check that a bit later as well.
next prev parent reply other threads:[~2015-09-01 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 17:36 [Qemu-devel] ARM softmmu breakpoint misbehavior Sergey Fedorov
2015-08-25 20:12 ` Christopher Covington
2015-08-28 19:21 ` Peter Maydell
2015-09-01 11:58 ` Sergey Fedorov [this message]
2015-09-02 16:53 ` Sergey Fedorov
2015-09-02 19:08 ` Sergey Fedorov
2015-09-02 19:45 ` Peter Maydell
2015-09-03 8:39 ` Sergey Fedorov
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=55E592DD.2030302@gmail.com \
--to=serge.fdrv@gmail.com \
--cc=peter.maydell@linaro.org \
--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).