diff options
author | Will Deacon <[email protected]> | 2024-04-23 16:05:17 +0100 |
---|---|---|
committer | Marc Zyngier <[email protected]> | 2024-05-01 16:47:45 +0100 |
commit | 58f3b0fc3b877447592301d14e7e1c05ebbad1a6 (patch) | |
tree | cfac012702d9dcccfd5652f2c9b7de80d0cd7274 /tools/perf/scripts/python/bin/stackcollapse-record | |
parent | 7cc1d214a6cd39d7af13f931c8134c24e33dd7f6 (diff) |
KVM: arm64: Support TLB invalidation in guest context
Typically, TLB invalidation of guest stage-2 mappings using nVHE is
performed by a hypercall originating from the host. For the invalidation
instruction to be effective, therefore, __tlb_switch_to_{guest,host}()
swizzle the active stage-2 context around the TLBI instruction.
With guest-to-host memory sharing and unsharing hypercalls
originating from the guest under pKVM, there is need to support
both guest and host VMID invalidations issued from guest context.
Replace the __tlb_switch_to_{guest,host}() functions with a more general
{enter,exit}_vmid_context() implementation which supports being invoked
from guest context and acts as a no-op if the target context matches the
running context.
Signed-off-by: Will Deacon <[email protected]>
Signed-off-by: Fuad Tabba <[email protected]>
Acked-by: Oliver Upton <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Marc Zyngier <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions