Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1718666
| From | Paolo Bonzini <pbonzini@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/4] KVM: nVMX: move vmentry tasks from prepare_vmcs12 to enter_vmx_non_root_mode |
| Date | 2017-08-23 23:50 +0200 |
| Message-ID | <uhLHb-5Vg-1@gated-at.bofh.it> (permalink) |
| References | <uhKL8-5jQ-13@gated-at.bofh.it> <uhKL8-5jQ-11@gated-at.bofh.it> <uhLnQ-5N6-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 23/08/2017 23:25, Jim Mattson wrote:
>> + if (from_vmentry) {
>> + vmcs12->launch_state = 1;
> Because we defer most guest state validity checks to the hardware
> vmlaunch of the vmcs02, it is too early to set the vmcs12 launched
> state here. If the exit reason has the high bit set,
> vmcs12->launch_state should not be modified.
Thanks---I'll do my homework and add a testcase then. :) The launched
state cannot be discovered with VMREAD, but I can test that a
VMLAUNCH;VMLAUNCH works and a VMLAUNCH;VMRESUME fails.
The same applies for the next instruction, which is part of step 6 of
the vmentry ("An event may be injected in the guest context"). This one
can be tested with VMREAD.
Paolo
>> +
>> + /* vm_entry_intr_info_field is cleared on exit. Emulate this
>> + * instead of reading the real value. */
>> + vmcs12->vm_entry_intr_info_field &= ~INTR_INFO_VALID_MASK;
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH 1/4] KVM: nVMX: move vmentry tasks from prepare_vmcs12 to enter_vmx_non_root_mode Paolo Bonzini <pbonzini@redhat.com> - 2017-08-23 22:50 +0200
Re: [PATCH 1/4] KVM: nVMX: move vmentry tasks from prepare_vmcs12 to enter_vmx_non_root_mode Jim Mattson <jmattson@google.com> - 2017-08-23 23:30 +0200
Re: [PATCH 1/4] KVM: nVMX: move vmentry tasks from prepare_vmcs12 to enter_vmx_non_root_mode Paolo Bonzini <pbonzini@redhat.com> - 2017-08-23 23:50 +0200
csiph-web