Re: [PATCH 3/3] KVM: nVMX: check for null vmcs12 when L1 does invept

2014-03-27 Thread Bandan Das
Jan Kiszka writes: > On 2014-03-26 21:22, Bandan Das wrote: >> Jan Kiszka writes: >> >>> On 2014-03-22 17:43, Bandan Das wrote: Jan Kiszka writes: > On 2014-03-20 21:58, Bandan Das wrote: >> Jan Kiszka writes: >> >>> On 2014-03-20 04:28, Bandan Das wrote: So

Re: [PATCH 3/3] KVM: nVMX: check for null vmcs12 when L1 does invept

2014-03-27 Thread Jan Kiszka
On 2014-03-26 21:22, Bandan Das wrote: > Jan Kiszka writes: > >> On 2014-03-22 17:43, Bandan Das wrote: >>> Jan Kiszka writes: >>> On 2014-03-20 21:58, Bandan Das wrote: > Jan Kiszka writes: > >> On 2014-03-20 04:28, Bandan Das wrote: >>> Some L1 hypervisors such as Xen see

Re: [PATCH 3/3] KVM: nVMX: check for null vmcs12 when L1 does invept

2014-03-26 Thread Bandan Das
Jan Kiszka writes: > On 2014-03-22 17:43, Bandan Das wrote: >> Jan Kiszka writes: >> >>> On 2014-03-20 21:58, Bandan Das wrote: Jan Kiszka writes: > On 2014-03-20 04:28, Bandan Das wrote: >> Some L1 hypervisors such as Xen seem to be calling invept after >> vmclear or bef

Re: [PATCH 3/3] KVM: nVMX: check for null vmcs12 when L1 does invept

2014-03-23 Thread Jan Kiszka
On 2014-03-22 17:43, Bandan Das wrote: > Jan Kiszka writes: > >> On 2014-03-20 21:58, Bandan Das wrote: >>> Jan Kiszka writes: >>> On 2014-03-20 04:28, Bandan Das wrote: > Some L1 hypervisors such as Xen seem to be calling invept after > vmclear or before vmptrld on L2. In this case

Re: [PATCH 3/3] KVM: nVMX: check for null vmcs12 when L1 does invept

2014-03-22 Thread Bandan Das
Jan Kiszka writes: > On 2014-03-20 21:58, Bandan Das wrote: >> Jan Kiszka writes: >> >>> On 2014-03-20 04:28, Bandan Das wrote: Some L1 hypervisors such as Xen seem to be calling invept after vmclear or before vmptrld on L2. In this case, proceed with falling through and syncing

Re: [PATCH 3/3] KVM: nVMX: check for null vmcs12 when L1 does invept

2014-03-22 Thread Jan Kiszka
On 2014-03-20 21:58, Bandan Das wrote: > Jan Kiszka writes: > >> On 2014-03-20 04:28, Bandan Das wrote: >>> Some L1 hypervisors such as Xen seem to be calling invept after >>> vmclear or before vmptrld on L2. In this case, proceed with >>> falling through and syncing roots as a case where >>> con

Re: [PATCH 3/3] KVM: nVMX: check for null vmcs12 when L1 does invept

2014-03-20 Thread Bandan Das
Paolo Bonzini writes: > Il 20/03/2014 04:28, Bandan Das ha scritto: >> Some L1 hypervisors such as Xen seem to be calling invept after >> vmclear or before vmptrld on L2. In this case, proceed with >> falling through and syncing roots as a case where >> context wide invalidation can't be supporte

Re: [PATCH 3/3] KVM: nVMX: check for null vmcs12 when L1 does invept

2014-03-20 Thread Bandan Das
Jan Kiszka writes: > On 2014-03-20 04:28, Bandan Das wrote: >> Some L1 hypervisors such as Xen seem to be calling invept after >> vmclear or before vmptrld on L2. In this case, proceed with >> falling through and syncing roots as a case where >> context wide invalidation can't be supported > > Ca

Re: [PATCH 3/3] KVM: nVMX: check for null vmcs12 when L1 does invept

2014-03-20 Thread Paolo Bonzini
Il 20/03/2014 04:28, Bandan Das ha scritto: Some L1 hypervisors such as Xen seem to be calling invept after vmclear or before vmptrld on L2. In this case, proceed with falling through and syncing roots as a case where context wide invalidation can't be supported Signed-off-by: Bandan Das --- a

Re: [PATCH 3/3] KVM: nVMX: check for null vmcs12 when L1 does invept

2014-03-20 Thread Jan Kiszka
On 2014-03-20 04:28, Bandan Das wrote: > Some L1 hypervisors such as Xen seem to be calling invept after > vmclear or before vmptrld on L2. In this case, proceed with > falling through and syncing roots as a case where > context wide invalidation can't be supported Can we also base this behaviour

[PATCH 3/3] KVM: nVMX: check for null vmcs12 when L1 does invept

2014-03-19 Thread Bandan Das
Some L1 hypervisors such as Xen seem to be calling invept after vmclear or before vmptrld on L2. In this case, proceed with falling through and syncing roots as a case where context wide invalidation can't be supported Signed-off-by: Bandan Das --- arch/x86/kvm/vmx.c | 5 +++-- 1 file changed, 3