From: Jim Mattson <jmattson@google.com>
To: seanjc@google.com, kvm@vger.kernel.org, pbonzini@redhat.com
Cc: Jim Mattson <jmattson@google.com>
Subject: [kvm-unit-tests PATCH 1/5] nVMX: Enable x2APIC mode for virtual-interrupt delivery tests
Date: Mon, 11 Dec 2023 10:55:48 -0800 [thread overview]
Message-ID: <20231211185552.3856862-2-jmattson@google.com> (raw)
In-Reply-To: <20231211185552.3856862-1-jmattson@google.com>
Since "virtualize x2APIC mode" is enabled for these tests, call
enable_x2apic() so that the x2apic_ops function table will be
installed.
Signed-off-by: Jim Mattson <jmattson@google.com>
---
x86/vmx_tests.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/x86/vmx_tests.c b/x86/vmx_tests.c
index c1540d396da8..e5ed79b7da4a 100644
--- a/x86/vmx_tests.c
+++ b/x86/vmx_tests.c
@@ -9305,6 +9305,7 @@ static void enable_vid(void)
assert(cpu_has_apicv());
+ enable_x2apic();
disable_intercept_for_x2apic_msrs();
virtual_apic_page = alloc_page();
--
2.43.0.472.g3155946c3a-goog
next prev parent reply other threads:[~2023-12-11 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 18:55 [kvm-unit-tests PATCH 0/5] nVMX: Simple posted interrupts test Jim Mattson
2023-12-11 18:55 ` Jim Mattson [this message]
2023-12-11 18:55 ` [kvm-unit-tests PATCH 2/5] nVMX: test nested "virtual-interrupt delivery" Jim Mattson
2023-12-11 18:55 ` [kvm-unit-tests PATCH 3/5] nVMX: test nested EOI virtualization Jim Mattson
2023-12-11 18:55 ` [kvm-unit-tests PATCH 4/5] nVMX: add self-IPI tests to vmx_basic_vid_test Jim Mattson
2023-12-11 18:55 ` [kvm-unit-tests PATCH 5/5] nVMX: add test for posted interrupts Jim Mattson
2024-06-05 23:20 ` [kvm-unit-tests PATCH 0/5] nVMX: Simple posted interrupts test Sean Christopherson
2024-10-09 6:48 ` Like Xu
2024-10-14 8:56 ` Chao Gao
2024-10-16 15:59 ` 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=20231211185552.3856862-2-jmattson@google.com \
--to=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@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