kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chao Gao <chao.gao@intel.com>
To: kvm@vger.kernel.org
Cc: "Chao Gao" <chao.gao@intel.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Liran Alon" <liran.alon@oracle.com>
Subject: [kvm-unit-tests PATCH] kvm-unit-tests: vmx: add a test for injecting events to halted L2
Date: Sun, 11 Feb 2018 10:06:47 +0800	[thread overview]
Message-ID: <1518314807-31821-1-git-send-email-chao.gao@intel.com> (raw)

This patch leverages existing "interrupt" tests. What the patch does is L1
puts L2 in halt state and injects an event to L2. Then check a flag to
identify whether event injection succeeds or not.

Cc: Liran Alon <liran.alon@oracle.com>
Signed-off-by: Chao Gao <chao.gao@intel.com>
---
 x86/vmx_tests.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/x86/vmx_tests.c b/x86/vmx_tests.c
index 0c3b5a7..3c46d3a 100644
--- a/x86/vmx_tests.c
+++ b/x86/vmx_tests.c
@@ -1584,6 +1584,12 @@ static void interrupt_main(void)
 	for (loops = 0; loops < 10000000 && !timer_fired; loops++)
 		asm volatile ("nop");
 	report("running a guest with interrupt acknowledgement set", timer_fired);
+
+	apic_write(APIC_TMICT, 0);
+	irq_enable();
+	timer_fired = false;
+	vmcall();
+	report("Inject an event to a halted guest", timer_fired);
 }
 
 static int interrupt_exit_handler(void)
@@ -1615,6 +1621,12 @@ static int interrupt_exit_handler(void)
 		case 6:
 			vmcs_write(GUEST_ACTV_STATE, ACTV_HLT);
 			break;
+
+		case 8:
+			vmcs_write(GUEST_ACTV_STATE, ACTV_HLT);
+			vmcs_write(ENT_INTR_INFO,
+				   TIMER_VECTOR | INTR_INFO_VALID_MASK);
+			break;
 		}
 		vmx_inc_test_stage();
 		vmcs_write(GUEST_RIP, guest_rip + insn_len);
-- 
1.9.1

                 reply	other threads:[~2018-02-11  2:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1518314807-31821-1-git-send-email-chao.gao@intel.com \
    --to=chao.gao@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=liran.alon@oracle.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.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;
as well as URLs for NNTP newsgroup(s).