From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Jim Mattson <jmattson@google.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
Oliver Upton <oupton@google.com>, Peter Shier <pshier@google.com>
Subject: [PATCH v5 25/27] KVM: selftests: Use uapi header to get VMX and SVM exit reasons/codes
Date: Tue, 30 Aug 2022 23:16:12 +0000 [thread overview]
Message-ID: <20220830231614.3580124-26-seanjc@google.com> (raw)
In-Reply-To: <20220830231614.3580124-1-seanjc@google.com>
Include the vmx.h and svm.h uapi headers that KVM so kindly provides
instead of manually defining all the same exit reasons/code.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
---
.../selftests/kvm/include/x86_64/svm_util.h | 7 +--
.../selftests/kvm/include/x86_64/vmx.h | 51 +------------------
2 files changed, 4 insertions(+), 54 deletions(-)
diff --git a/tools/testing/selftests/kvm/include/x86_64/svm_util.h b/tools/testing/selftests/kvm/include/x86_64/svm_util.h
index a339b537a575..7aee6244ab6a 100644
--- a/tools/testing/selftests/kvm/include/x86_64/svm_util.h
+++ b/tools/testing/selftests/kvm/include/x86_64/svm_util.h
@@ -9,15 +9,12 @@
#ifndef SELFTEST_KVM_SVM_UTILS_H
#define SELFTEST_KVM_SVM_UTILS_H
+#include <asm/svm.h>
+
#include <stdint.h>
#include "svm.h"
#include "processor.h"
-#define SVM_EXIT_EXCP_BASE 0x040
-#define SVM_EXIT_HLT 0x078
-#define SVM_EXIT_MSR 0x07c
-#define SVM_EXIT_VMMCALL 0x081
-
struct svm_test_data {
/* VMCB */
struct vmcb *vmcb; /* gva */
diff --git a/tools/testing/selftests/kvm/include/x86_64/vmx.h b/tools/testing/selftests/kvm/include/x86_64/vmx.h
index 99fa1410964c..e4206f69b716 100644
--- a/tools/testing/selftests/kvm/include/x86_64/vmx.h
+++ b/tools/testing/selftests/kvm/include/x86_64/vmx.h
@@ -8,6 +8,8 @@
#ifndef SELFTEST_KVM_VMX_H
#define SELFTEST_KVM_VMX_H
+#include <asm/vmx.h>
+
#include <stdint.h>
#include "processor.h"
#include "apic.h"
@@ -100,55 +102,6 @@
#define VMX_EPT_VPID_CAP_AD_BITS 0x00200000
#define EXIT_REASON_FAILED_VMENTRY 0x80000000
-#define EXIT_REASON_EXCEPTION_NMI 0
-#define EXIT_REASON_EXTERNAL_INTERRUPT 1
-#define EXIT_REASON_TRIPLE_FAULT 2
-#define EXIT_REASON_INTERRUPT_WINDOW 7
-#define EXIT_REASON_NMI_WINDOW 8
-#define EXIT_REASON_TASK_SWITCH 9
-#define EXIT_REASON_CPUID 10
-#define EXIT_REASON_HLT 12
-#define EXIT_REASON_INVD 13
-#define EXIT_REASON_INVLPG 14
-#define EXIT_REASON_RDPMC 15
-#define EXIT_REASON_RDTSC 16
-#define EXIT_REASON_VMCALL 18
-#define EXIT_REASON_VMCLEAR 19
-#define EXIT_REASON_VMLAUNCH 20
-#define EXIT_REASON_VMPTRLD 21
-#define EXIT_REASON_VMPTRST 22
-#define EXIT_REASON_VMREAD 23
-#define EXIT_REASON_VMRESUME 24
-#define EXIT_REASON_VMWRITE 25
-#define EXIT_REASON_VMOFF 26
-#define EXIT_REASON_VMON 27
-#define EXIT_REASON_CR_ACCESS 28
-#define EXIT_REASON_DR_ACCESS 29
-#define EXIT_REASON_IO_INSTRUCTION 30
-#define EXIT_REASON_MSR_READ 31
-#define EXIT_REASON_MSR_WRITE 32
-#define EXIT_REASON_INVALID_STATE 33
-#define EXIT_REASON_MWAIT_INSTRUCTION 36
-#define EXIT_REASON_MONITOR_INSTRUCTION 39
-#define EXIT_REASON_PAUSE_INSTRUCTION 40
-#define EXIT_REASON_MCE_DURING_VMENTRY 41
-#define EXIT_REASON_TPR_BELOW_THRESHOLD 43
-#define EXIT_REASON_APIC_ACCESS 44
-#define EXIT_REASON_EOI_INDUCED 45
-#define EXIT_REASON_EPT_VIOLATION 48
-#define EXIT_REASON_EPT_MISCONFIG 49
-#define EXIT_REASON_INVEPT 50
-#define EXIT_REASON_RDTSCP 51
-#define EXIT_REASON_PREEMPTION_TIMER 52
-#define EXIT_REASON_INVVPID 53
-#define EXIT_REASON_WBINVD 54
-#define EXIT_REASON_XSETBV 55
-#define EXIT_REASON_APIC_WRITE 56
-#define EXIT_REASON_INVPCID 58
-#define EXIT_REASON_PML_FULL 62
-#define EXIT_REASON_XSAVES 63
-#define EXIT_REASON_XRSTORS 64
-#define LAST_EXIT_REASON 64
enum vmcs_field {
VIRTUAL_PROCESSOR_ID = 0x00000000,
--
2.37.2.672.g94769d06f0-goog
next prev parent reply other threads:[~2022-08-30 23:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 23:15 [PATCH v5 00/27] KVM: x86: Event/exception fixes and cleanups Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 01/27] KVM: nVMX: Unconditionally purge queued/injected events on nested "exit" Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 02/27] KVM: VMX: Drop bits 31:16 when shoving exception error code into VMCS Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 03/27] KVM: x86: Don't check for code breakpoints when emulating on exception Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 04/27] KVM: x86: Allow clearing RFLAGS.RF on forced emulation to test code #DBs Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 05/27] KVM: x86: Suppress code #DBs on Intel if MOV/POP SS blocking is active Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 06/27] KVM: nVMX: Treat General Detect #DB (DR7.GD=1) as fault-like Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 07/27] KVM: nVMX: Prioritize TSS T-flag #DBs over Monitor Trap Flag Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 08/27] KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 09/27] KVM: x86: Use DR7_GD macro instead of open coding check in emulator Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 10/27] KVM: nVMX: Ignore SIPI that arrives in L2 when vCPU is not in WFS Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 11/27] KVM: nVMX: Unconditionally clear mtf_pending on nested VM-Exit Sean Christopherson
2022-08-30 23:15 ` [PATCH v5 12/27] KVM: VMX: Inject #PF on ENCLS as "emulated" #PF Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 13/27] KVM: x86: Rename kvm_x86_ops.queue_exception to inject_exception Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 14/27] KVM: x86: Make kvm_queued_exception a properly named, visible struct Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 15/27] KVM: x86: Formalize blocking of nested pending exceptions Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 16/27] KVM: x86: Use kvm_queue_exception_e() to queue #DF Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 17/27] KVM: x86: Hoist nested event checks above event injection logic Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 18/27] KVM: x86: Evaluate ability to inject SMI/NMI/IRQ after potential VM-Exit Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 19/27] KVM: nVMX: Add a helper to identify low-priority #DB traps Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 20/27] KVM: nVMX: Document priority of all known events on Intel CPUs Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 21/27] KVM: x86: Morph pending exceptions to pending VM-Exits at queue time Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 22/27] KVM: x86: Treat pending TRIPLE_FAULT requests as pending exceptions Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 23/27] KVM: VMX: Update MTF and ICEBP comments to document KVM's subtle behavior Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 24/27] KVM: x86: Rename inject_pending_events() to kvm_check_and_inject_events() Sean Christopherson
2022-08-30 23:16 ` Sean Christopherson [this message]
2022-08-30 23:16 ` [PATCH v5 26/27] KVM: selftests: Add an x86-only test to verify nested exception queueing Sean Christopherson
2022-08-30 23:16 ` [PATCH v5 27/27] KVM: x86: Allow force_emulation_prefix to be written without a reload Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220830231614.3580124-26-seanjc@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=oupton@google.com \
--cc=pbonzini@redhat.com \
--cc=pshier@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®