On Tue, 2018-04-10 at 11:04 +0200, Paolo Bonzini wrote:
> On 10/04/2018 10:50, KarimAllah Ahmed wrote:
> >
> > WARN_ON(preemptible());
> > - if (!kvm_x86_ops->set_hv_timer)
> > + if (!kvm_x86_ops->has_hv_timer ||
> > + !kvm_x86_ops->has_hv_timer(apic->vcpu))
> > return fa
On 10/04/2018 10:50, KarimAllah Ahmed wrote:
> WARN_ON(preemptible());
> - if (!kvm_x86_ops->set_hv_timer)
> + if (!kvm_x86_ops->has_hv_timer ||
> + !kvm_x86_ops->has_hv_timer(apic->vcpu))
> return false;
>
> if (!apic_lvtt_period(apic) && atomic_read(&kt
The VMX-preemption timer is used by KVM as a way to set deadlines for the
guest (i.e. timer emulation). That was safe till very recently when
capability KVM_X86_DISABLE_EXITS_MWAIT to disable intercepting MWAIT was
introduced. According to Intel SDM 25.5.1:
"""
The VMX-preemption timer operates in
3 matches
Mail list logo