From: Richard Henderson <richard.henderson@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>, qemu-devel@nongnu.org
Cc: Eduardo Habkost <eduardo@habkost.net>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v3 1/2] target/i386: fix hang when using slow path for ptw_setl
Date: Tue, 29 Oct 2024 15:47:08 +0000 [thread overview]
Message-ID: <1d3e5017-f0ee-4dbd-b4b9-5e97c56d63e7@linaro.org> (raw)
In-Reply-To: <20241025175857.2554252-2-pierrick.bouvier@linaro.org>
On 10/25/24 18:58, Pierrick Bouvier wrote:
> When instrumenting memory accesses for plugin, we force memory accesses
> to use the slow path for mmu [1]. This create a situation where we end
> up calling ptw_setl_slow. This was fixed recently in [2] but the issue
> still could appear out of plugins use case.
>
> Since this function gets called during a cpu_exec, start_exclusive then
> hangs. This exclusive section was introduced initially for security
> reasons [3].
>
> I suspect this code path was never triggered, because ptw_setl_slow
> would always be called transitively from cpu_exec, resulting in a hang.
>
> [1]https://gitlab.com/qemu-project/qemu/-/commit/6d03226b42247b68ab2f0b3663e0f624335a4055
> [2]https://gitlab.com/qemu-project/qemu/-/commit/115ade42d50144c15b74368d32dc734ea277d853
> [3]https://gitlab.com/qemu-project/qemu/-/issues/279
>
> Fixes:https://gitlab.com/qemu-project/qemu/-/issues/2566
> Signed-off-by: Pierrick Bouvier<pierrick.bouvier@linaro.org>
> ---
> target/i386/tcg/sysemu/excp_helper.c | 5 +++++
> 1 file changed, 5 insertions(+)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2024-10-29 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 17:58 [PATCH v3 0/2] target/i386: fix hang when using slow path for ptw_setl Pierrick Bouvier
2024-10-25 17:58 ` [PATCH v3 1/2] " Pierrick Bouvier
2024-10-29 15:47 ` Richard Henderson [this message]
2024-11-17 3:49 ` Michael Tokarev
2024-11-18 2:54 ` Pierrick Bouvier
2024-10-25 17:58 ` [PATCH v3 2/2] cpu: ensure we don't call start_exclusive from cpu_exec Pierrick Bouvier
2024-10-26 4:54 ` Philippe Mathieu-Daudé
2024-11-04 22:25 ` [PATCH v3 0/2] target/i386: fix hang when using slow path for ptw_setl Pierrick Bouvier
2024-11-12 15:47 ` Richard Henderson
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=1d3e5017-f0ee-4dbd-b4b9-5e97c56d63e7@linaro.org \
--to=richard.henderson@linaro.org \
--cc=eduardo@habkost.net \
--cc=pbonzini@redhat.com \
--cc=pierrick.bouvier@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).