diff options
author | Oliver Upton <[email protected]> | 2024-06-20 16:46:43 +0000 |
---|---|---|
committer | Oliver Upton <[email protected]> | 2024-06-20 19:02:40 +0000 |
commit | 9092aca9fe9aa986b573355affdd190710a906c0 (patch) | |
tree | 0f422804d9b69c205edbb8f211b35fe6caf77bb6 /tools/perf/util/trace-event-scripting.c | |
parent | b7e5c9426429aa64cacc2d804417e0e5f79b8b60 (diff) |
KVM: arm64: nv: Use guest hypervisor's max VL when running nested guest
The max VL for nested guests is additionally constrained by the max VL
selected by the guest hypervisor. Use that instead of KVM's max VL when
running a nested guest.
Note that the guest hypervisor's ZCR_EL2 is sanitised against the VM's
max VL at the time of access, so there's no additional handling required
at the time of use.
Reviewed-by: Marc Zyngier <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Oliver Upton <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions