KVM: arm64: nv: Add handling of range-based TLBI operations

Browse source

We already support some form of range operation by handling FEAT_TTL,
but so far the "arbitrary" range operations are unsupported.

Let's fix that.

For EL2 S1, this is simple enough: we just map both NSH, ISH and OSH
instructions onto the ISH version for EL1.

For TLBI instructions affecting EL1 S1, we use the same model as
their non-range counterpart to invalidate in the context of the
correct VMID.

For TLBI instructions affecting S2, we interpret the data passed
by the guest to compute the range and use that to tear-down part
of the shadow S2 range and invalidate the TLBs.

Finally, we advertise FEAT_TLBIRANGE if the host supports it.

Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20240614144552.2773592-16-maz@kernel.org
Signed-off-by: Oliver Upton <oliver.upton@linux.dev>

...

This commit is contained in:

Marc Zyngier 2024-06-14 15:45:51 +01:00 • committed by Oliver Upton

parent 0cb8aae226

commit 5d476ca57d

3 changed files with 108 additions and 6 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

26

arch/arm64/kvm/hyp/vhe/tlb.c

View file

8

arch/arm64/kvm/nested.c

View file

80

arch/arm64/kvm/sys_regs.c

View file