From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>
Subject: Re: [PATCH v5 0/4] KVM: LAPIC: Implement Exitless Timer
Date: Tue, 2 Jul 2019 18:38:56 +0200 [thread overview]
Message-ID: <1fbd236a-f7f9-e66a-e08c-bf2bac901d15@redhat.com> (raw)
In-Reply-To: <1561110002-4438-1-git-send-email-wanpengli@tencent.com>
On 21/06/19 11:39, Wanpeng Li wrote:
> Dedicated instances are currently disturbed by unnecessary jitter due
> to the emulated lapic timers fire on the same pCPUs which vCPUs resident.
> There is no hardware virtual timer on Intel for guest like ARM. Both
> programming timer in guest and the emulated timer fires incur vmexits.
> This patchset tries to avoid vmexit which is incurred by the emulated
> timer fires in dedicated instance scenario.
>
> When nohz_full is enabled in dedicated instances scenario, the unpinned
> timer will be moved to the nearest busy housekeepers after commit
> 9642d18eee2cd (nohz: Affine unpinned timers to housekeepers) and commit
> 444969223c8 ("sched/nohz: Fix affine unpinned timers mess"). However,
> KVM always makes lapic timer pinned to the pCPU which vCPU residents, the
> reason is explained by commit 61abdbe0 (kvm: x86: make lapic hrtimer
> pinned). Actually, these emulated timers can be offload to the housekeeping
> cpus since APICv is really common in recent years. The guest timer interrupt
> is injected by posted-interrupt which is delivered by housekeeping cpu
> once the emulated timer fires.
>
> The host admin should fine tuned, e.g. dedicated instances scenario w/
> nohz_full cover the pCPUs which vCPUs resident, several pCPUs surplus
> for busy housekeeping, disable mwait/hlt/pause vmexits to keep in non-root
> mode, ~3% redis performance benefit can be observed on Skylake server.
Marcelo,
does this patch work for you or can you still see the oops?
Thanks,
Paolo
> w/o patchset:
>
> VM-EXIT Samples Samples% Time% Min Time Max Time Avg time
>
> EXTERNAL_INTERRUPT 42916 49.43% 39.30% 0.47us 106.09us 0.71us ( +- 1.09% )
>
> w/ patchset:
>
> VM-EXIT Samples Samples% Time% Min Time Max Time Avg time
>
> EXTERNAL_INTERRUPT 6871 9.29% 2.96% 0.44us 57.88us 0.72us ( +- 4.02% )
>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Krčmář <rkrcmar@redhat.com>
> Cc: Marcelo Tosatti <mtosatti@redhat.com>
>
> v4 -> v5:
> * update patch description in patch 1/4
> * feed latest apic->lapic_timer.expired_tscdeadline to kvm_wait_lapic_expire()
> * squash advance timer handling to patch 2/4
>
> v3 -> v4:
> * drop the HRTIMER_MODE_ABS_PINNED, add kick after set pending timer
> * don't posted inject already-expired timer
>
> v2 -> v3:
> * disarming the vmx preemption timer when posted_interrupt_inject_timer_enabled()
> * check kvm_hlt_in_guest instead
>
> v1 -> v2:
> * check vcpu_halt_in_guest
> * move module parameter from kvm-intel to kvm
> * add housekeeping_enabled
> * rename apic_timer_expired_pi to kvm_apic_inject_pending_timer_irqs
>
>
> Wanpeng Li (4):
> KVM: LAPIC: Make lapic timer unpinned
> KVM: LAPIC: Inject timer interrupt via posted interrupt
> KVM: LAPIC: Ignore timer migration when lapic timer is injected by pi
> KVM: LAPIC: Don't inject already-expired timer via posted interrupt
>
> arch/x86/kvm/lapic.c | 68 +++++++++++++++++++++++++++--------------
> arch/x86/kvm/lapic.h | 3 +-
> arch/x86/kvm/svm.c | 2 +-
> arch/x86/kvm/vmx/vmx.c | 5 +--
> arch/x86/kvm/x86.c | 11 ++++---
> arch/x86/kvm/x86.h | 2 ++
> include/linux/sched/isolation.h | 2 ++
> kernel/sched/isolation.c | 6 ++++
> 8 files changed, 67 insertions(+), 32 deletions(-)
>
next prev parent reply other threads:[~2019-07-02 16:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 9:39 Wanpeng Li
2019-06-21 9:39 ` [PATCH v5 1/4] KVM: LAPIC: Make lapic timer unpinned Wanpeng Li
2019-06-21 9:40 ` [PATCH v5 2/4] KVM: LAPIC: Inject timer interrupt via posted interrupt Wanpeng Li
2019-07-05 12:37 ` Paolo Bonzini
[not found] ` <HK2PR02MB4145E122DC5AC2445137A10F80F50@HK2PR02MB4145.apcprd02.prod.outlook.com>
2019-07-05 13:00 ` Paolo Bonzini
[not found] ` <HK2PR02MB4145BBA5B72DD70AC622FD0E80F50@HK2PR02MB4145.apcprd02.prod.outlook.com>
2019-07-05 13:42 ` Paolo Bonzini
2019-06-21 9:40 ` [PATCH v5 3/4] KVM: LAPIC: Ignore timer migration when lapic timer is injected by pi Wanpeng Li
2019-06-21 9:40 ` [PATCH v5 4/4] KVM: LAPIC: Don't inject already-expired timer via posted interrupt Wanpeng Li
2019-07-05 12:40 ` Paolo Bonzini
[not found] ` <HK2PR02MB4145B13227997511174DBFA480F50@HK2PR02MB4145.apcprd02.prod.outlook.com>
2019-07-05 13:26 ` Paolo Bonzini
2019-07-02 16:38 ` Paolo Bonzini [this message]
2019-07-02 22:23 ` [PATCH v5 0/4] KVM: LAPIC: Implement Exitless Timer Marcelo Tosatti
2019-07-03 0:47 ` Wanpeng Li
2019-07-03 1:01 ` 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=1fbd236a-f7f9-e66a-e08c-bf2bac901d15@redhat.com \
--to=pbonzini@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=rkrcmar@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
Powered by JetHome