KVM: arm64: Fix incorrect comment on kvm_get_hyp_vector()
authorDavid Brazdil <dbrazdil@google.com>
Fri, 15 May 2020 15:25:50 +0000 (16:25 +0100)
committerMarc Zyngier <maz@kernel.org>
Mon, 25 May 2020 15:16:16 +0000 (16:16 +0100)
The comment used to say that kvm_get_hyp_vector is only called on VHE systems.
In fact, it is also called from the nVHE init function cpu_init_hyp_mode().
Fix the comment to stop confusing devs.

Signed-off-by: David Brazdil <dbrazdil@google.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20200515152550.83810-1-dbrazdil@google.com
arch/arm64/include/asm/kvm_mmu.h

index 30b0e8d6b8953f03b6ef71e902b11daa2b11d858..796f6a2e794abcef38de0d1b1aee64278052b53b 100644 (file)
@@ -473,7 +473,7 @@ static inline int kvm_write_guest_lock(struct kvm *kvm, gpa_t gpa,
 extern void *__kvm_bp_vect_base;
 extern int __kvm_harden_el2_vector_slot;
 
-/*  This is only called on a VHE system */
+/*  This is called on both VHE and !VHE systems */
 static inline void *kvm_get_hyp_vector(void)
 {
        struct bp_hardening_data *data = arm64_get_bp_hardening_data();