From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>
Cc: pbonzini@redhat.com, richard.henderson@linaro.org,
qemu-devel@nongnu.org, peterx@redhat.com, david@redhat.com
Subject: Re: [PATCH v2 2/3] softmmu: fix watchpoint-interrupt races
Date: Thu, 11 Nov 2021 13:15:34 +0000 [thread overview]
Message-ID: <87lf1uj0fp.fsf@linaro.org> (raw)
In-Reply-To: <163662451431.125458.14945698834107669531.stgit@pasha-ThinkPad-X280>
Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru> writes:
> Watchpoint may be processed in two phases. First one is detecting
> the instruction with target memory access. And the second one is
> executing only one instruction and setting the debug interrupt flag.
> Hardware interrupts can break this sequence when they happen after
> the first watchpoint phase.
> This patch postpones the interrupt request until watchpoint is
> processed.
>
> Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgalyuk@ispras.ru>
> ---
> accel/tcg/cpu-exec.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/accel/tcg/cpu-exec.c b/accel/tcg/cpu-exec.c
> index df12452b8f..e4526c2f5e 100644
> --- a/accel/tcg/cpu-exec.c
> +++ b/accel/tcg/cpu-exec.c
> @@ -742,6 +742,11 @@ static inline bool cpu_handle_interrupt(CPUState *cpu,
> qemu_mutex_unlock_iothread();
> return true;
> }
> + /* Process watchpoints first, or interrupts will ruin everything */
> + if (cpu->watchpoint_hit) {
> + qemu_mutex_unlock_iothread();
> + return false;
> + }
side note: I wonder if it is time to wrap up the locks up with
QEMU_LOCK_GUARD or something similar?
Anyway seems reasonable:
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
next prev parent reply other threads:[~2021-11-11 13:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 9:55 [PATCH v2 0/3] Some watchpoint-related patches Pavel Dovgalyuk
2021-11-11 9:55 ` [PATCH v2 1/3] icount: preserve cflags when custom tb is about to execute Pavel Dovgalyuk
2021-11-11 12:20 ` Alex Bennée
2021-11-16 7:40 ` Pavel Dovgalyuk
2021-11-16 10:57 ` Alex Bennée
2021-11-17 9:47 ` Alex Bennée
2021-11-17 10:03 ` Richard Henderson
2021-11-17 10:29 ` Alex Bennée
2021-11-17 11:29 ` Richard Henderson
2021-11-18 11:05 ` Pavel Dovgalyuk
2021-11-11 9:55 ` [PATCH v2 2/3] softmmu: fix watchpoint-interrupt races Pavel Dovgalyuk
2021-11-11 13:15 ` Alex Bennée [this message]
2021-11-12 10:10 ` David Hildenbrand
2021-11-11 9:55 ` [PATCH v2 3/3] softmmu: fix watchpoints on memory used by vCPU internals Pavel Dovgalyuk
2021-11-11 10:48 ` [PATCH v2 0/3] Some watchpoint-related patches David Hildenbrand
2021-11-11 10:50 ` Pavel Dovgalyuk
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=87lf1uj0fp.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=david@redhat.com \
--cc=pavel.dovgalyuk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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.