From: Wanpeng Li <kernellwp@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>, "Radim Krčmář" <rkrcmar@redhat.com>,
"Wanpeng Li" <wanpeng.li@hotmail.com>
Subject: Re: [PATCH] KVM: X86: Fix preempt the preemption timer cancel
Date: Sat, 27 May 2017 06:07:13 +0800 [thread overview]
Message-ID: <CANRm+CxTMG2VZ1W+tkJr9FmB__qGyQrSyWiWsEZ6zZf8yiJ34A@mail.gmail.com> (raw)
In-Reply-To: <bc2e59ad-de5b-0209-8d9e-25f17eb9fa00@redhat.com>
2017-05-26 23:57 GMT+08:00 Paolo Bonzini <pbonzini@redhat.com>:
>
>
> On 21/05/2017 05:32, Wanpeng Li wrote:
>> CPU0 CPU1
>>
>> vmx_cancel_hv_timer
>> vCPU0's vmx->hv_deadline_tsc = -1
>>
>> preempt occur
>>
>> clear preemption timer field in CPU1's active vmcs
>> vCPU0's apic_timer.hv_timer_in_use = false
>> vmx_vcpu_run(vCPU0)
>> vmx_arm_hv_timer
>> if (vmx->hv_deadline_tsc == -1)
>> nothing change
>>
>> handle_preemption_timer(vCPU0)
>> kvm_lapic_expired_hv_timer
>> WARN_ON(!apic->lapic_timer.hv_timer_in_use);
>
>
> I think it's more like this, what do you think?
>
> CPU0 CPU1
>
> preemption timer vmexit
> handle_preemption_timer(vCPU0)
> kvm_lapic_expired_hv_timer
> vmx_cancel_hv_timer
> vmx->hv_deadline_tsc = -1
> vmcs_clear_bits
> /* hv_timer_in_use still true */
> sched_out
> sched_in
> kvm_arch_vcpu_load
> vmx_set_hv_timer
> write vmx->hv_deadline_tsc
> vmcs_set_bits
> /* back in kvm_lapic_expired_hv_timer */
> hv_timer_in_use = false
> ...
> vmx_vcpu_run
> vmx_arm_hv_run
> write preemption timer deadline
> spurious preemption timer vmexit
> handle_preemption_timer(vCPU0)
> kvm_lapic_expired_hv_timer
> WARN_ON(!apic->lapic_timer.hv_timer_in_use);
Looks good to me, thanks for your help, Paolo. :)
Regards,
Wanpeng Li
prev parent reply other threads:[~2017-05-27 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 3:32 Wanpeng Li
2017-05-26 15:45 ` Paolo Bonzini
2017-05-26 15:57 ` Paolo Bonzini
2017-05-26 22:07 ` Wanpeng Li [this message]
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=CANRm+CxTMG2VZ1W+tkJr9FmB__qGyQrSyWiWsEZ6zZf8yiJ34A@mail.gmail.com \
--to=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=wanpeng.li@hotmail.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
all inboxes | Powered by JetHome®