Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1551356pxb; Thu, 28 Oct 2021 05:58:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwL2IXTykjdC28OO4H0xafdco0ygWPYhXZZfxBiDVdom64s1Mvy7yFU6VN+PX4pT2x0H7Wq X-Received: by 2002:a62:1848:0:b0:47b:e426:ac7a with SMTP id 69-20020a621848000000b0047be426ac7amr4144462pfy.14.1635425904403; Thu, 28 Oct 2021 05:58:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635425904; cv=none; d=google.com; s=arc-20160816; b=DAB7WCj6lJXOis5qV4MFBSjQtMSykGRyM7IXnBHGXfAM2SK3vsalfx0rkgzYqHNduI WcUgKZ0QUdF+DkJDdNev+gP2vu8+YKIuyr+l9JlNzx/FcRrNZEA83m2Tn+n9Dvlbj0nC u5B+glLGh1VYHP0nRDy1VfVXD1MFfrIU5uiG3/YQtjEopshLNEWBTfhwxWkVPbXpycAT Pt1DiqwSVdnCijQ8+zGFRPfE6gEjaYwrCdATLv0az09uGmqD/e+XiZJBxk+7ZLmzImLq ud1qv/NTDopEP9Hc+cui2fLmTAe1ETBRF/NsajIwTJiPUpTeKT6r5DlBORPvrIUqN5GU AWQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=AzVqjh+2Lud5A9V6SBUfySTC7Jdhp9VKIE8pHEMoxEM=; b=FWOEd4OWp7UASMv0M5Ge9xJwX43tacT4PDehkkESKLXHb5yQzYQ5iTzmnqtzM349aw Gioiclrxf63kQ0tpNu7q0Cjq+Y1yY/pF5k5g4iI1ubfcBV67Aj1CRwRODQRzz6ZTkHXH o9O/uOAQ01hmzB6V5vtHUxd9Fbl8tECv/zSgJvlUdic+A5X0wyZDDAqr5uUOd/IbiRgO icnq4/Rme+yccLkXCHGNyLYLP1rdzMueZ3kGCzC9EGlBRQYwgCoPrh3BXZqSCbbkXRbd CqkSKD1T3jgpRieXYJI34NhRnZYxGmUIgGKyQx3RRPMKJhAUbOpzM9mJwgXbKzh93VEp rgxw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Haw4meDn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p3si2063006pfh.201.2021.10.28.05.58.11; Thu, 28 Oct 2021 05:58:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Haw4meDn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230267AbhJ1M4E (ORCPT + 99 others); Thu, 28 Oct 2021 08:56:04 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:25900 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229998AbhJ1M4D (ORCPT ); Thu, 28 Oct 2021 08:56:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1635425616; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=AzVqjh+2Lud5A9V6SBUfySTC7Jdhp9VKIE8pHEMoxEM=; b=Haw4meDnnZiRNqepWdJFiqTa/PAiOvLV38FWXEXwIlArT5exwBdzbYcE1nm/SYMwkwnJbn Ruv4+XnNWlHbMrY2qYwYy/lyn4TIq6WxuxbJqteBHV67OKIFlK7nuqtNeEApmcAEeQ2k7W m/EJaZj3ddTXLnSZSkrsgaZt9w5ABmc= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-212-ldzfqrMaMG-LB-zAjma-Rg-1; Thu, 28 Oct 2021 08:53:33 -0400 X-MC-Unique: ldzfqrMaMG-LB-zAjma-Rg-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E1F24802682; Thu, 28 Oct 2021 12:53:28 +0000 (UTC) Received: from starship (unknown [10.40.194.243]) by smtp.corp.redhat.com (Postfix) with ESMTP id 03E025DA61; Thu, 28 Oct 2021 12:53:12 +0000 (UTC) Message-ID: <558e7e4c36e649709837079a25c2f56fc5609fbe.camel@redhat.com> Subject: Re: [PATCH v2 28/43] KVM: VMX: Remove vCPU from PI wakeup list before updating PID.NV From: Maxim Levitsky To: Sean Christopherson , Marc Zyngier , Huacai Chen , Aleksandar Markovic , Paul Mackerras , Anup Patel , Paul Walmsley , Palmer Dabbelt , Albert Ou , Christian Borntraeger , Janosch Frank , Paolo Bonzini Cc: James Morse , Alexandru Elisei , Suzuki K Poulose , Atish Patra , David Hildenbrand , Cornelia Huck , Claudio Imbrenda , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, linux-mips@vger.kernel.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, David Matlack , Oliver Upton , Jing Zhang Date: Thu, 28 Oct 2021 15:53:11 +0300 In-Reply-To: <20211009021236.4122790-29-seanjc@google.com> References: <20211009021236.4122790-1-seanjc@google.com> <20211009021236.4122790-29-seanjc@google.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2021-10-08 at 19:12 -0700, Sean Christopherson wrote: > Remove the vCPU from the wakeup list before updating the notification > vector in the posted interrupt post-block helper. There is no need to > wake the current vCPU as it is by definition not blocking. Practically > speaking this is a nop as it only shaves a few meager cycles in the > unlikely case that the vCPU was migrated and the previous pCPU gets a > wakeup IRQ right before PID.NV is updated. The real motivation is to > allow for more readable code in the future, when post-block is merged > with vmx_vcpu_pi_load(), at which point removal from the list will be > conditional on the old notification vector. > > Opportunistically add comments to document why KVM has a per-CPU spinlock > that, at first glance, appears to be taken only on the owning CPU. > Explicitly call out that the spinlock must be taken with IRQs disabled, a > detail that was "lost" when KVM switched from spin_lock_irqsave() to > spin_lock(), with IRQs disabled for the entirety of the relevant path. > > Signed-off-by: Sean Christopherson > --- > arch/x86/kvm/vmx/posted_intr.c | 49 +++++++++++++++++++++++----------- > 1 file changed, 33 insertions(+), 16 deletions(-) > > diff --git a/arch/x86/kvm/vmx/posted_intr.c b/arch/x86/kvm/vmx/posted_intr.c > index 2b2206339174..901b7a5f7777 100644 > --- a/arch/x86/kvm/vmx/posted_intr.c > +++ b/arch/x86/kvm/vmx/posted_intr.c > @@ -10,10 +10,22 @@ > #include "vmx.h" > > /* > - * We maintain a per-CPU linked-list of vCPU, so in wakeup_handler() we > - * can find which vCPU should be waken up. > + * Maintain a per-CPU list of vCPUs that need to be awakened by wakeup_handler() Nit: While at it, it would be nice to rename this to pi_wakeup_hanlder() so that it can be more easilly found. > + * when a WAKEUP_VECTOR interrupted is posted. vCPUs are added to the list when > + * the vCPU is scheduled out and is blocking (e.g. in HLT) with IRQs enabled. s/interrupted/interrupt ? Isn't that comment incorrect? As I see, the PI hardware is setup to use the WAKEUP_VECTOR when vcpu blocks (in pi_pre_block) and then that vcpu is added to the list. The pi_wakeup_hanlder just goes over the list and wakes up all vcpus on the lsit. > + * The vCPUs posted interrupt descriptor is updated at the same time to set its > + * notification vector to WAKEUP_VECTOR, so that posted interrupt from devices > + * wake the target vCPUs. vCPUs are removed from the list and the notification > + * vector is reset when the vCPU is scheduled in. > */ > static DEFINE_PER_CPU(struct list_head, blocked_vcpu_on_cpu); Also while at it, why not to rename this to 'blocked_vcpu_list'? to explain that this is list of blocked vcpus. Its a per-cpu variable so 'on_cpu' suffix isn't needed IMHO. > +/* > + * Protect the per-CPU list with a per-CPU spinlock to handle task migration. > + * When a blocking vCPU is awakened _and_ migrated to a different pCPU, the > + * ->sched_in() path will need to take the vCPU off the list of the _previous_ > + * CPU. IRQs must be disabled when taking this lock, otherwise deadlock will > + * occur if a wakeup IRQ arrives and attempts to acquire the lock. > + */ > static DEFINE_PER_CPU(spinlock_t, blocked_vcpu_on_cpu_lock); > > static inline struct pi_desc *vcpu_to_pi_desc(struct kvm_vcpu *vcpu) > @@ -101,23 +113,28 @@ static void __pi_post_block(struct kvm_vcpu *vcpu) > WARN(pi_desc->nv != POSTED_INTR_WAKEUP_VECTOR, > "Wakeup handler not enabled while the vCPU was blocking"); > > - dest = cpu_physical_id(vcpu->cpu); > - if (!x2apic_mode) > - dest = (dest << 8) & 0xFF00; > - > - do { > - old.control = new.control = READ_ONCE(pi_desc->control); > - > - new.ndst = dest; > - > - /* set 'NV' to 'notification vector' */ > - new.nv = POSTED_INTR_VECTOR; > - } while (cmpxchg64(&pi_desc->control, old.control, > - new.control) != old.control); > - > + /* > + * Remove the vCPU from the wakeup list of the _previous_ pCPU, which > + * will not be the same as the current pCPU if the task was migrated. > + */ > spin_lock(&per_cpu(blocked_vcpu_on_cpu_lock, vcpu->pre_pcpu)); > list_del(&vcpu->blocked_vcpu_list); > spin_unlock(&per_cpu(blocked_vcpu_on_cpu_lock, vcpu->pre_pcpu)); > + > + dest = cpu_physical_id(vcpu->cpu); > + if (!x2apic_mode) > + dest = (dest << 8) & 0xFF00; It would be nice to have a function for this, this appears in this file twice. Maybe there is a function already somewhere? > + > + do { > + old.control = new.control = READ_ONCE(pi_desc->control); > + > + new.ndst = dest; > + > + /* set 'NV' to 'notification vector' */ > + new.nv = POSTED_INTR_VECTOR; > + } while (cmpxchg64(&pi_desc->control, old.control, > + new.control) != old.control); > + > vcpu->pre_pcpu = -1; > } > Best regards, Maxim Levitsky