diff options
| author | 2022-08-30 15:37:12 +0200 | |
|---|---|---|
| committer | 2022-09-26 12:02:42 -0400 | |
| commit | 6cce93de28c23ca0272111ec1eeeee4da6545722 (patch) | |
| tree | 0db846832b131b436d69dace70972e5346b91c05 /tools/testing/selftests/exec/git:/ssh:/git@git.zx2c4.com | |
| parent | KVM: nVMX: Refactor unsupported eVMCS controls logic to use 2-d array (diff) | |
| download | linux-dev-6cce93de28c23ca0272111ec1eeeee4da6545722.tar.xz linux-dev-6cce93de28c23ca0272111ec1eeeee4da6545722.zip | |
KVM: nVMX: Use CC() macro to handle eVMCS unsupported controls checks
Locally #define and use the nested virtualization Consistency Check (CC)
macro to handle eVMCS unsupported controls checks. Using the macro loses
the existing printing of the unsupported controls, but that's a feature
and not a bug. The existing approach is flawed because the @err param to
trace_kvm_nested_vmenter_failed() is the error code, not the error value.
The eVMCS trickery mostly works as __print_symbolic() falls back to
printing the raw hex value, but that subtly relies on not having a match
between the unsupported value and VMX_VMENTER_INSTRUCTION_ERRORS.
If it's really truly necessary to snapshot the bad value, then the
tracepoint can be extended in the future.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Link: https://lore.kernel.org/r/20220830133737.1539624-9-vkuznets@redhat.com
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/testing/selftests/exec/git:/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions
