summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2024-06-14 17:45:43 +0300
committerOliver Upton <oliver.upton@linux.dev>2024-06-19 11:14:37 +0300
commit8e236efa4cd2df8b270784a33d7e334933789f1a (patch)
tree2c90f19b82c0572125b11b23e6e177aa78358dab /tools/perf/scripts/python/exported-sql-viewer.py
parent67fda56e76da4c4be9a8502d7211dbba024576d2 (diff)
downloadlinux-8e236efa4cd2df8b270784a33d7e334933789f1a.tar.xz
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/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions