diff options
author | Sean Christopherson <seanjc@google.com> | 2022-07-15 23:21:05 +0000 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-07-28 13:22:23 -0400 |
commit | 65e3b446bcceaac7448cb25a2a5bf4adbcf25fe6 (patch) | |
tree | dd5e5776e0af18ba40210e94f8cca7209cb951c5 /arch/x86/kvm/mmu/tdp_mmu.h | |
parent | a8ac499bb6abbd55fe60f1dc2d053f4b5b13aa73 (diff) | |
download | linux-65e3b446bcceaac7448cb25a2a5bf4adbcf25fe6.tar.bz2 |
KVM: x86/mmu: Document the "rules" for using host_pfn_mapping_level()
Add a comment to document how host_pfn_mapping_level() can be used safely,
as the line between safe and dangerous is quite thin. E.g. if KVM were
to ever support in-place promotion to create huge pages, consuming the
level is safe if the caller holds mmu_lock and checks that there's an
existing _leaf_ SPTE, but unsafe if the caller only checks that there's a
non-leaf SPTE.
Opportunistically tweak the existing comments to explicitly document why
KVM needs to use READ_ONCE().
No functional change intended.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20220715232107.3775620-3-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/kvm/mmu/tdp_mmu.h')
0 files changed, 0 insertions, 0 deletions