From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <kernellwp@gmail.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 v3] KVM: LAPIC: Fix lapic timer injection delay
Date: Thu, 29 Jun 2017 13:43:05 +0200 [thread overview]
Message-ID: <b23e1e52-4dae-201f-3be5-00d79c06d62c@redhat.com> (raw)
In-Reply-To: <CANRm+CyYiSAn+HnaDY=qJAx6HRFsKVyWmuUpQr50f1CaQQjVew@mail.gmail.com>
On 29/06/2017 10:44, Wanpeng Li wrote:
>>> You still need to enable the preemption timer even if you return 1, so
>>> in lapic.c it becomes
>>>
>>> if (!apic_lvtt_period(apic)) {
>>> if (r)
>>> apic_timer_expired(apic);
>>> if (atomic_read(&apic->lapic_timer.pending))
>>> need_cancel = true;
>>> }
>> I think the codes are more clear but the same as above. We didn't
>> program preemption timer vmcs field if delta == 0, so how to
>> understand "need to enable the preemption timer even if return 1"?
> I guess you mean start_hv_timer() should return true, right?
vmx.c's set_hv_timer callback should set the preemption timer execution
control. Otherwise, kvm_lapic_hv_timer_expired is again not called.
Paolo
next prev parent reply other threads:[~2017-06-29 11:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 1:29 Wanpeng Li
2017-06-28 12:10 ` Paolo Bonzini
2017-06-28 13:55 ` Wanpeng Li
2017-06-28 14:00 ` Paolo Bonzini
2017-06-28 14:05 ` Wanpeng Li
2017-06-28 14:27 ` Wanpeng Li
2017-06-28 14:30 ` Paolo Bonzini
2017-06-29 3:42 ` Wanpeng Li
2017-06-29 7:55 ` Paolo Bonzini
2017-06-29 8:17 ` Wanpeng Li
2017-06-29 8:44 ` Wanpeng Li
2017-06-29 11:43 ` Paolo Bonzini [this message]
2017-06-29 11:54 ` Wanpeng Li
2017-06-29 12:05 ` Wanpeng Li
2017-06-29 12:13 ` Paolo Bonzini
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=b23e1e52-4dae-201f-3be5-00d79c06d62c@redhat.com \
--to=pbonzini@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®