From: Aili Yao <yaoaili126@gmail.com>
To: Sean Christopherson <seanjc@google.com>
Cc: pbonzini@redhat.com, vkuznets@redhat.com, wanpengli@tencent.com,
jmattson@google.com, joro@8bytes.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, yaoaili@kingsoft.com
Subject: Re: [PATCH v2] KVM: LAPIC: Per vCPU control over kvm_can_post_timer_interrupt
Date: Fri, 10 Dec 2021 11:47:28 +0800 [thread overview]
Message-ID: <20211210114728.043f9437@gmail.com> (raw)
In-Reply-To: <YbJJCf20VdHNnpzY@google.com>
On Thu, 9 Dec 2021 18:20:57 +0000
Sean Christopherson <seanjc@google.com> wrote:
> On Wed, Dec 08, 2021, Aili Yao wrote:
> > On Tue, 7 Dec 2021 23:23:03 +0000
> > Sean Christopherson <seanjc@google.com> wrote:
> >
> > >
> > > static bool kvm_can_post_timer_interrupt(struct kvm_vcpu *vcpu)
> > > {
> > > - return pi_inject_timer && kvm_vcpu_apicv_active(vcpu);
> > > + return pi_inject_timer && kvm_vcpu_apicv_active(vcpu) &&
> > > + (kvm_mwait_in_guest(vcpu) || kvm_hlt_in_guest(vcpu));
> > > }
> > >
> > > bool kvm_can_use_hv_timer(struct kvm_vcpu *vcpu)
> > > {
> > > - return kvm_x86_ops.set_hv_timer
> > > - && !(kvm_mwait_in_guest(vcpu->kvm) ||
> > > - kvm_can_post_timer_interrupt(vcpu));
> > > + /*
> > > + * Don't use the hypervisor timer, a.k.a. VMX Preemption Timer, if the
> > > + * guest can execute MWAIT without exiting as the timer will stop
> > > + * counting if the core enters C3 or lower. HLT in the guest is ok as
> > > + * HLT is effectively C1 and the timer counts in C0, C1, and C2.
> > > + *
> > > + * Don't use the hypervisor timer if KVM can post a timer interrupt to
> > > + * the guest since posted the timer avoids taking an extra a VM-Exit
> > > + * when the timer expires.
> > > + */
> > > + return kvm_x86_ops.set_hv_timer &&
> > > + !kvm_mwait_in_guest(vcpu->kvm) &&
> > > + !kvm_can_post_timer_interrupt(vcpu));
> > > }
> > > EXPORT_SYMBOL_GPL(kvm_can_use_hv_timer);
> > >
> >
> > Sorry, I am little confused here now:
> > if kvm_can_post_timer_interrupt(vcpu) return true(cpu-pm enabled), then the kvm_can_use_hv_timer will always be false;
> > if kvm_can_post_timer_interrupt(vcpu) return false(cpu-pm disable),then kvm_mwait_in_guest(vcpu->kvm) can't be true ether;
> > It seems we don't need kvm_mwait_in_guest(vcpu->kvm) here?
>
> We do, it's to prevent the guest from enter C3+ and stopping the VMX preemption
> timer, e.g. if either kvm_vcpu_apicv_active() or pi_inject_timer evaluates false.
Great thanks for your explanation!
Now i am clear!
--Aili Yao
next prev parent reply other threads:[~2021-12-10 3:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 4:54 [PATCH v2] KVM: LAPIC: Per vCPU control over kvm_can_post_timer_interrupt Aili Yao
2021-12-07 23:23 ` Sean Christopherson
2021-12-08 3:36 ` Aili Yao
2021-12-08 10:21 ` Aili Yao
2021-12-09 18:20 ` Sean Christopherson
2021-12-10 3:47 ` Aili Yao [this message]
2021-12-16 8:23 ` Aili Yao
2021-12-16 15:45 ` Sean Christopherson
2021-12-17 2:22 ` Aili Yao
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=20211210114728.043f9437@gmail.com \
--to=yaoaili126@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--cc=yaoaili@kingsoft.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