diff options
author | 2024-06-14 15:45:43 +0100 | |
---|---|---|
committer | 2024-06-19 08:14:37 +0000 | |
commit | 8e236efa4cd2df8b270784a33d7e334933789f1a (patch) | |
tree | 2c90f19b82c0572125b11b23e6e177aa78358dab /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | KVM: arm64: nv: Handle EL2 Stage-1 TLB invalidation (diff) | |
download | wireguard-linux-8e236efa4cd2df8b270784a33d7e334933789f1a.tar.xz wireguard-linux-8e236efa4cd2df8b270784a33d7e334933789f1a.zip |
KVM: arm64: nv: Handle TLB invalidation targeting L2 stage-1
While dealing with TLB invalidation targeting the guest hypervisor's
own stage-1 was easy, doing the same thing for its own guests is
a bit more involved.
Since such an invalidation is scoped by VMID, it needs to apply to
all s2_mmu contexts that have been tagged by that VMID, irrespective
of the value of VTTBR_EL2.BADDR.
So for each s2_mmu context matching that VMID, we invalidate the
corresponding TLBs, each context having its own "physical" VMID.
Co-developed-by: Jintack Lim <jintack.lim@linaro.org>
Co-developed-by: Christoffer Dall <christoffer.dall@arm.com>
Signed-off-by: Jintack Lim <jintack.lim@linaro.org>
Signed-off-by: Christoffer Dall <christoffer.dall@arm.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20240614144552.2773592-8-maz@kernel.org
Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions