From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: "Liran Alon" <liran.alon@oracle.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"kvm list" <kvm@vger.kernel.org>,
"Jim Mattson" <jmattson@google.com>,
vkuznets@redhat.com
Subject: Re: [PATCH kvm-unit-tests 0/8]: x86: vmx: Test INIT processing in various CPU VMX states
Date: Tue, 1 Oct 2019 16:34:08 -0700 [thread overview]
Message-ID: <20191001233408.GB6151@linux.intel.com> (raw)
In-Reply-To: <20191001184034.GC27090@linux.intel.com>
On Tue, Oct 01, 2019 at 11:40:34AM -0700, Sean Christopherson wrote:
> Anyways, I'll double check that the INIT should indeed be consumed as part
> of the VM-Exit.
Confirmed that the INIT is cleared prior to delivering VM-Exit.
next prev parent reply other threads:[~2019-10-01 23:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 12:52 [PATCH kvm-unit-tests 0/8]: x86: vmx: Test INIT processing in various CPU VMX states Liran Alon
2019-09-19 12:52 ` [PATCH kvm-unit-tests 1/8] x86: vmx: Refactor init of VMX caps to separate function Liran Alon
2019-09-19 12:52 ` [PATCH kvm-unit-tests 2/8] x86: vmx: Prepare init_vmx() for VMX support on AP CPUs Liran Alon
2019-09-19 12:52 ` [PATCH kvm-unit-tests 3/8] x86: vmx: Expose vmx_init() to be used " Liran Alon
2019-09-19 12:52 ` [PATCH kvm-unit-tests 4/8] x86: vmx: Support VMXON on AP CPUs VMX region Liran Alon
2019-09-19 12:52 ` [PATCH kvm-unit-tests 5/8] x86: vmx: Use MSR_IA32_FEATURE_CONTROL bits names Liran Alon
2019-09-19 12:52 ` [PATCH kvm-unit-tests 6/8] x86: vmx: Expose util to enable VMX in MSR_IA32_FEATURE_CONTROL Liran Alon
2019-09-19 12:52 ` [PATCH kvm-unit-tests 7/8] x86: vmx: Allow tests to hand-over test-vmcs between CPUs Liran Alon
2019-09-19 12:52 ` [PATCH kvm-unit-tests 8/8] x86: vmx: Test INIT processing during various CPU VMX states Liran Alon
2019-09-19 14:08 ` [PATCH kvm-unit-tests 0/8]: x86: vmx: Test INIT processing in " Vitaly Kuznetsov
2019-09-24 15:34 ` Liran Alon
2019-09-24 15:42 ` Paolo Bonzini
2019-09-25 23:57 ` Liran Alon
2019-09-26 8:47 ` Paolo Bonzini
2019-09-30 23:02 ` Nadav Amit
2019-10-01 0:48 ` Liran Alon
2019-10-01 1:14 ` Nadav Amit
2019-10-01 1:23 ` Liran Alon
2019-10-01 1:29 ` Nadav Amit
2019-10-01 18:40 ` Sean Christopherson
2019-10-01 23:21 ` Sean Christopherson
2019-10-01 23:34 ` Sean Christopherson [this message]
2019-10-01 23:37 ` Nadav Amit
2019-10-02 0:10 ` Liran Alon
2019-10-02 0:19 ` Liran Alon
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=20191001233408.GB6151@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=nadav.amit@gmail.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=vkuznets@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.