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>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Marc Zyngier" <Marc.Zyngier@arm.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v4 1/6] KVM: Fix leak vCPU's VMCS value into other pCPU
Date: Tue, 6 Aug 2019 01:17:27 +0200 [thread overview]
Message-ID: <9acbc733-442f-0f65-9b56-ff800a3fa0f5@redhat.com> (raw)
In-Reply-To: <1564970604-10044-1-git-send-email-wanpengli@tencent.com>
On 05/08/19 04:03, Wanpeng Li wrote:
> From: Wanpeng Li <wanpengli@tencent.com>
>
> After commit d73eb57b80b (KVM: Boost vCPUs that are delivering interrupts), a
> five years old bug is exposed. Running ebizzy benchmark in three 80 vCPUs VMs
> on one 80 pCPUs Skylake server, a lot of rcu_sched stall warning splatting
> in the VMs after stress testing:
>
> INFO: rcu_sched detected stalls on CPUs/tasks: { 4 41 57 62 77} (detected by 15, t=60004 jiffies, g=899, c=898, q=15073)
> Call Trace:
> flush_tlb_mm_range+0x68/0x140
> tlb_flush_mmu.part.75+0x37/0xe0
> tlb_finish_mmu+0x55/0x60
> zap_page_range+0x142/0x190
> SyS_madvise+0x3cd/0x9c0
> system_call_fastpath+0x1c/0x21
>
> swait_active() sustains to be true before finish_swait() is called in
> kvm_vcpu_block(), voluntarily preempted vCPUs are taken into account
> by kvm_vcpu_on_spin() loop greatly increases the probability condition
> kvm_arch_vcpu_runnable(vcpu) is checked and can be true, when APICv
> is enabled the yield-candidate vCPU's VMCS RVI field leaks(by
> vmx_sync_pir_to_irr()) into spinning-on-a-taken-lock vCPU's current
> VMCS.
>
> This patch fixes it by checking conservatively a subset of events.
>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Krčmář <rkrcmar@redhat.com>
> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
> Cc: Marc Zyngier <Marc.Zyngier@arm.com>
> Cc: stable@vger.kernel.org
> Fixes: 98f4a1467 (KVM: add kvm_arch_vcpu_runnable() test to kvm_vcpu_on_spin() loop)
> Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
> ---
> v3 -> v4:
> * just test KVM_REQ_*
> * rename the hook to apicv_has_pending_interrupt
> * wrap with #ifdef CONFIG_KVM_ASYNC_PF
> v2 -> v3:
> * check conservatively a subset of events
> v1 -> v2:
> * checking swait_active(&vcpu->wq) for involuntary preemption
>
> arch/mips/kvm/mips.c | 5 +++++
> arch/powerpc/kvm/powerpc.c | 5 +++++
> arch/s390/kvm/kvm-s390.c | 5 +++++
> arch/x86/include/asm/kvm_host.h | 1 +
> arch/x86/kvm/svm.c | 6 ++++++
> arch/x86/kvm/vmx/vmx.c | 6 ++++++
> arch/x86/kvm/x86.c | 16 ++++++++++++++++
> include/linux/kvm_host.h | 1 +
> virt/kvm/arm/arm.c | 5 +++++
> virt/kvm/kvm_main.c | 16 +++++++++++++++-
> 10 files changed, 65 insertions(+), 1 deletion(-)
>
> diff --git a/arch/mips/kvm/mips.c b/arch/mips/kvm/mips.c
> index 2cfe839..95a4642 100644
> --- a/arch/mips/kvm/mips.c
> +++ b/arch/mips/kvm/mips.c
> @@ -98,6 +98,11 @@ int kvm_arch_vcpu_runnable(struct kvm_vcpu *vcpu)
> return !!(vcpu->arch.pending_exceptions);
> }
>
> +bool kvm_arch_dy_runnable(struct kvm_vcpu *vcpu)
Using a __weak definition for the default implementation is a bit more
concise. Queued with that change.
Paolo
next prev parent reply other threads:[~2019-08-05 23:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 2:03 [PATCH v4 1/6] KVM: Fix leak vCPU's VMCS value into other pCPU Wanpeng Li
2019-08-05 2:03 ` [PATCH v4 2/6] KVM: LAPIC: Don't need to wakeup vCPU twice afer timer fire Wanpeng Li
2019-08-05 2:03 ` [PATCH v4 3/6] KVM: Check preempted_in_kernel for involuntary preemption Wanpeng Li
2019-08-05 2:03 ` [PATCH v4 4/6] KVM: X86: Use IPI shorthands in kvm guest when support Wanpeng Li
2019-08-05 2:03 ` [PATCH v4 5/6] KVM: LAPIC: Add pv ipi tracepoint Wanpeng Li
2019-08-05 2:03 ` [PATCH v4 6/6] KVM: X86: Add pv tlb shootdown tracepoint Wanpeng Li
2019-08-05 23:17 ` Paolo Bonzini [this message]
2019-08-06 0:35 ` [PATCH v4 1/6] KVM: Fix leak vCPU's VMCS value into other pCPU Wanpeng Li
2019-08-06 6:20 ` Paolo Bonzini
2019-08-22 0:46 ` Wanpeng Li
2019-08-22 8:35 ` Paolo Bonzini
2019-08-22 8:45 ` 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=9acbc733-442f-0f65-9b56-ff800a3fa0f5@redhat.com \
--to=pbonzini@redhat.com \
--cc=Marc.Zyngier@arm.com \
--cc=borntraeger@de.ibm.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).