* [PATCH v2 0/2] target/i386: fix hang when using slow path for ptw_setl
@ 2024-10-25 17:53 Pierrick Bouvier
2024-10-25 17:53 ` [PATCH v2 1/2] " Pierrick Bouvier
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Pierrick Bouvier @ 2024-10-25 17:53 UTC (permalink / raw)
To: qemu-devel
Cc: Richard Henderson, Paolo Bonzini, Eduardo Habkost,
Pierrick Bouvier
Most of the details are available in first patch. Second one is there to ensure
we'll have a useful error message if start_exclusive is called from cpu_exec
again.
I'm a bit puzzled that we never triggered this hang before. Is there something
wrong with the potential slow path for ptw_setl, or is it simply very uncommon?
v2:
- get current cpu from local variable instead of current_cpu global var.
- change condition to check cpu is running as current_cpu will never be NULL.
Pierrick Bouvier (2):
target/i386: fix hang when using slow path for ptw_setl
cpu: ensure we don't call start_exclusive from cpu_exec
cpu-common.c | 3 +++
target/i386/tcg/sysemu/excp_helper.c | 4 ++++
2 files changed, 7 insertions(+)
--
2.39.5
^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH v2 1/2] target/i386: fix hang when using slow path for ptw_setl
2024-10-25 17:53 [PATCH v2 0/2] target/i386: fix hang when using slow path for ptw_setl Pierrick Bouvier
@ 2024-10-25 17:53 ` Pierrick Bouvier
2024-10-25 17:53 ` [PATCH v2 2/2] cpu: ensure we don't call start_exclusive from cpu_exec Pierrick Bouvier
2024-10-25 17:59 ` [PATCH v2 0/2] target/i386: fix hang when using slow path for ptw_setl Pierrick Bouvier
2 siblings, 0 replies; 4+ messages in thread
From: Pierrick Bouvier @ 2024-10-25 17:53 UTC (permalink / raw)
To: qemu-devel
Cc: Richard Henderson, Paolo Bonzini, Eduardo Habkost,
Pierrick Bouvier
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.
Since this function gets called during a cpu_exec, start_exclusive then
hangs. This exclusive section was introduced initially for security
reasons [2].
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/-/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 | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/target/i386/tcg/sysemu/excp_helper.c b/target/i386/tcg/sysemu/excp_helper.c
index da187c8792a..e0436c7a672 100644
--- a/target/i386/tcg/sysemu/excp_helper.c
+++ b/target/i386/tcg/sysemu/excp_helper.c
@@ -107,6 +107,9 @@ static bool ptw_setl_slow(const PTETranslate *in, uint32_t old, uint32_t new)
{
uint32_t cmp;
+ /* We are in cpu_exec, and start_exclusive can't be called directly.*/
+ g_assert(current_cpu && current_cpu->running);
+ cpu_exec_end(current_cpu);
/* Does x86 really perform a rmw cycle on mmio for ptw? */
start_exclusive();
cmp = cpu_ldl_mmuidx_ra(in->env, in->gaddr, in->ptw_idx, 0);
@@ -114,6 +117,7 @@ static bool ptw_setl_slow(const PTETranslate *in, uint32_t old, uint32_t new)
cpu_stl_mmuidx_ra(in->env, in->gaddr, new, in->ptw_idx, 0);
}
end_exclusive();
+ cpu_exec_start(current_cpu);
return cmp == old;
}
--
2.39.5
^ permalink raw reply related [flat|nested] 4+ messages in thread
* [PATCH v2 2/2] cpu: ensure we don't call start_exclusive from cpu_exec
2024-10-25 17:53 [PATCH v2 0/2] target/i386: fix hang when using slow path for ptw_setl Pierrick Bouvier
2024-10-25 17:53 ` [PATCH v2 1/2] " Pierrick Bouvier
@ 2024-10-25 17:53 ` Pierrick Bouvier
2024-10-25 17:59 ` [PATCH v2 0/2] target/i386: fix hang when using slow path for ptw_setl Pierrick Bouvier
2 siblings, 0 replies; 4+ messages in thread
From: Pierrick Bouvier @ 2024-10-25 17:53 UTC (permalink / raw)
To: qemu-devel
Cc: Richard Henderson, Paolo Bonzini, Eduardo Habkost,
Pierrick Bouvier
Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
---
cpu-common.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/cpu-common.c b/cpu-common.c
index 6b262233a3b..c979138fce9 100644
--- a/cpu-common.c
+++ b/cpu-common.c
@@ -194,6 +194,9 @@ void start_exclusive(void)
CPUState *other_cpu;
int running_cpus;
+ /* Ensure we are not running, or start_exclusive will be blocked. */
+ g_assert(!current_cpu || !current_cpu->running);
+
if (current_cpu->exclusive_context_count) {
current_cpu->exclusive_context_count++;
return;
--
2.39.5
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH v2 0/2] target/i386: fix hang when using slow path for ptw_setl
2024-10-25 17:53 [PATCH v2 0/2] target/i386: fix hang when using slow path for ptw_setl Pierrick Bouvier
2024-10-25 17:53 ` [PATCH v2 1/2] " Pierrick Bouvier
2024-10-25 17:53 ` [PATCH v2 2/2] cpu: ensure we don't call start_exclusive from cpu_exec Pierrick Bouvier
@ 2024-10-25 17:59 ` Pierrick Bouvier
2 siblings, 0 replies; 4+ messages in thread
From: Pierrick Bouvier @ 2024-10-25 17:59 UTC (permalink / raw)
To: qemu-devel; +Cc: Richard Henderson, Paolo Bonzini, Eduardo Habkost
On 10/25/24 10:53, Pierrick Bouvier wrote:
> Most of the details are available in first patch. Second one is there to ensure
> we'll have a useful error message if start_exclusive is called from cpu_exec
> again.
>
> I'm a bit puzzled that we never triggered this hang before. Is there something
> wrong with the potential slow path for ptw_setl, or is it simply very uncommon?
>
> v2:
> - get current cpu from local variable instead of current_cpu global var.
> - change condition to check cpu is running as current_cpu will never be NULL.
>
> Pierrick Bouvier (2):
> target/i386: fix hang when using slow path for ptw_setl
> cpu: ensure we don't call start_exclusive from cpu_exec
>
> cpu-common.c | 3 +++
> target/i386/tcg/sysemu/excp_helper.c | 4 ++++
> 2 files changed, 7 insertions(+)
>
Pushed from my old branch (same as v1), please see v3 instead.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-10-25 18:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-10-25 17:53 [PATCH v2 0/2] target/i386: fix hang when using slow path for ptw_setl Pierrick Bouvier
2024-10-25 17:53 ` [PATCH v2 1/2] " Pierrick Bouvier
2024-10-25 17:53 ` [PATCH v2 2/2] cpu: ensure we don't call start_exclusive from cpu_exec Pierrick Bouvier
2024-10-25 17:59 ` [PATCH v2 0/2] target/i386: fix hang when using slow path for ptw_setl Pierrick Bouvier
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).