From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 1/3] KVM: LAPIC: Make lapic timer unpinned when timer is injected by posted-interrupt
Date: Mon, 10 Jun 2019 19:11:10 +0200 [thread overview]
Message-ID: <20190610171110.GB8389@flask> (raw)
In-Reply-To: <1559799086-13912-2-git-send-email-wanpengli@tencent.com>
2019-06-06 13:31+0800, Wanpeng Li:
> From: Wanpeng Li <wanpengli@tencent.com>
>
> Make lapic timer unpinned when timer is injected by posted-interrupt,
> the emulated timer can be offload to the housekeeping cpus.
>
> The host admin should fine tuned, e.g. dedicated instances scenario
> w/ nohz_full cover the pCPUs which vCPUs resident, several pCPUs
> surplus for housekeeping, disable mwait/hlt/pause vmexits to occupy
> the pCPUs, fortunately preemption timer is disabled after mwait is
> exposed to guest which makes emulated timer offload can be possible.
>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Krčmář <rkrcmar@redhat.com>
> Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
> ---
> arch/x86/kvm/lapic.c | 20 ++++++++++++++++----
> arch/x86/kvm/x86.c | 5 +++++
> arch/x86/kvm/x86.h | 2 ++
> include/linux/sched/isolation.h | 2 ++
> kernel/sched/isolation.c | 6 ++++++
> 5 files changed, 31 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> index fcf42a3..09b7387 100644
> --- a/arch/x86/kvm/lapic.c
> +++ b/arch/x86/kvm/lapic.c
> @@ -127,6 +127,12 @@ static inline u32 kvm_x2apic_id(struct kvm_lapic *apic)
> return apic->vcpu->vcpu_id;
> }
>
> +static inline bool posted_interrupt_inject_timer_enabled(struct kvm_vcpu *vcpu)
> +{
> + return pi_inject_timer && kvm_vcpu_apicv_active(vcpu) &&
> + kvm_mwait_in_guest(vcpu->kvm);
I'm torn about the mwait dependency. It covers a lot of the targeted
user base, but the relation is convoluted and not fitting perfectly.
What do you think about making posted_interrupt_inject_timer_enabled()
just
pi_inject_timer && kvm_vcpu_apicv_active(vcpu)
and disarming the vmx preemption timer when
posted_interrupt_inject_timer_enabled(), just like we do with mwait now?
Thanks.
next prev parent reply other threads:[~2019-06-10 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 5:31 [PATCH v2 0/3] KVM: LAPIC: Implement Exitless Timer Wanpeng Li
2019-06-06 5:31 ` [PATCH v2 1/3] KVM: LAPIC: Make lapic timer unpinned when timer is injected by posted-interrupt Wanpeng Li
2019-06-10 17:11 ` Radim Krčmář [this message]
2019-06-11 8:31 ` Wanpeng Li
2019-06-06 5:31 ` [PATCH v2 2/3] KVM: LAPIC: lapic timer interrupt is injected by posted interrupt Wanpeng Li
2019-06-10 16:51 ` Radim Krčmář
2019-06-11 8:18 ` Wanpeng Li
2019-06-11 11:40 ` Paolo Bonzini
2019-06-11 12:18 ` Wanpeng Li
2019-06-06 5:31 ` [PATCH v2 3/3] KVM: LAPIC: Ignore timer migration when lapic timer is injected by posted-interrupt Wanpeng Li
2019-06-06 10:55 ` [PATCH v2 4/3] KVM: LAPIC: add advance timer support to pi_inject_timer Wanpeng Li
2019-06-10 4:32 ` [PATCH v2 0/3] KVM: LAPIC: Implement Exitless Timer Wanpeng Li
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=20190610171110.GB8389@flask \
--to=rkrcmar@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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