summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/task-analyzer.py
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2026-10-15 11:05:34 +0100
committerMarc Zyngier <maz@kernel.org>2026-10-15 14:52:11 +0100
commit1d4ce2901f1e25b06d447c0b02d105d6dd3550d8 (patch)
treee4565585db9dda7bd527c21250d6db633f8284b3 /tools/perf/scripts/python/task-analyzer.py
parent21d3b33234ebbb675c2a2a0fa7b12d2d83953d7a (diff)
KVM: arm64: Move OUTSIDE_GUEST_MODE publication past context being saved
OUTSIDE_GUEST_MODE indicates to the rest of KVM that the vcpu has exited. So far, this is set as soon as we return from the notional hypervisor (which with VHE is just a function call away). However, code that uses OUTSIDE_GUEST_MODE as a synchronisation point relies on the vcpu state to have been written back to the in-memory structures. Clearly, this is not what is happening. Move the publication of OUTSIDE_GUEST_MODE to the point where the state is actually written, and give this write release semantics to ensure the correct ordering. Cc: stable@vger.kernel.org Reviewed-by: Fuad Tabba <fuad.tabba@linux.dev> Tested-by: Fuad Tabba <fuad.tabba@linux.dev> Link: https://patch.msgid.link/20261015100539.1011760-3-maz@kernel.org Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions