summaryrefslogtreecommitdiffstats
path: root/tools/bpf
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2024-02-27 18:41:34 -0800
committerPaolo Bonzini <pbonzini@redhat.com>2024-05-07 11:59:17 -0400
commit9b62e03e192ce9300608f9be69be9854a166eae3 (patch)
tree36c2339efe836b10511a544bd2b3ea750760de7c /tools/bpf
parent63b6206e2f9a4ca756262a8bc20fb869d6db52be (diff)
downloadlinux-stable-9b62e03e192ce9300608f9be69be9854a166eae3.tar.gz
linux-stable-9b62e03e192ce9300608f9be69be9854a166eae3.tar.bz2
linux-stable-9b62e03e192ce9300608f9be69be9854a166eae3.zip
KVM: x86: Define more SEV+ page fault error bits/flags for #NPF
Define more #NPF error code flags that are relevant to SEV+ (mostly SNP) guests, as specified by the APM: * Bit 31 (RMP): Set to 1 if the fault was caused due to an RMP check or a VMPL check failure, 0 otherwise. * Bit 34 (ENC): Set to 1 if the guest’s effective C-bit was 1, 0 otherwise. * Bit 35 (SIZEM): Set to 1 if the fault was caused by a size mismatch between PVALIDATE or RMPADJUST and the RMP, 0 otherwise. * Bit 36 (VMPL): Set to 1 if the fault was caused by a VMPL permission check failure, 0 otherwise. Note, the APM is *extremely* misleading, and strongly implies that the above flags can _only_ be set for #NPF exits from SNP guests. That is a lie, as bit 34 (C-bit=1, i.e. was encrypted) can be set when running _any_ flavor of SEV guest on SNP capable hardware. Signed-off-by: Sean Christopherson <seanjc@google.com> Message-ID: <20240228024147.41573-4-seanjc@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/bpf')
0 files changed, 0 insertions, 0 deletions