Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp4378585imw; Tue, 12 Jul 2022 07:02:50 -0700 (PDT) X-Google-Smtp-Source: AGRyM1s25vFC9id+rWQV8XWx01y3BgRWs7WsiY3Qknpo9Np6zbwEfv2n/N//fpCl1OVtnSh9CXeT X-Received: by 2002:a17:906:7007:b0:6ff:8028:42e with SMTP id n7-20020a170906700700b006ff8028042emr24326705ejj.278.1657634570245; Tue, 12 Jul 2022 07:02:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657634570; cv=none; d=google.com; s=arc-20160816; b=LuWjXZ19PSRInm/JBi4Y1p4PqS/an2VhHjloq0+lkCXqt6Q1IKy1GqXZjWwv3pRDl8 BOpKWMSXQZZuAq8Nczx5QnYxoTpW8M5OJ69DnYBOllHmkoo1P1cz9DtVnAfPfmzLArP4 l6LL3OKZFrMztZG65SjW0sb7x5DpDC8OkYK4ZDk2wE+JCedD5LWXWeFgKBtz11swDDNr 2IEgOINAeuX2myFciHfN0CxMm83CtNdPIpHCR4opRNPaaxR8ta7zfgpz993bLxbh379i F2FMkHbni6fFWxdWqULYJCeVyYgSe3wM8zFS/8/6bcMgbQtTmHPoSwRMeHWgLvqu+sIa lDjg== 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=LtXyCz0IEfDkRQV6tTiEfKs8tnmrH7wPrOPUpSOgUsI=; b=PgaKoYT4Bfkt2fLSxXeVGDzNbztx5zJyIQUNekteIGi3yc5ACd/MOusBYRxC//fATs gNd6EYVKTuLZazp2DDoU7cDNanKCPVuxoo8J80MoCNENHZdb30pVB8UgU9Pyv1yn43ug LpzJ9vwvWYgplwA6IYLi1QyKTUvAdR6ELf42vn/gM9zMC3btD6WS6ncmnIQCcGu1gvyH /4JkhIB4E4eredQlxppBdOvSnBopC8Ah/08VGp7IeEcSputW+QTPaljr8W9Pb7+FhkXr QaRUYudKaSyTNWKnmZQ6X0UUiAz4ZYyULZtFlXgm93s8n0P3an9Mk0A9c/D9+EUMv83u +XDg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=VYUw4EwW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b14-20020a056402350e00b0043ac55ccf10si15214954edd.620.2022.07.12.07.02.17; Tue, 12 Jul 2022 07:02:50 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=VYUw4EwW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S233413AbiGLNmw (ORCPT + 99 others); Tue, 12 Jul 2022 09:42:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55252 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233174AbiGLNmh (ORCPT ); Tue, 12 Jul 2022 09:42:37 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 325C6B96BA for ; Tue, 12 Jul 2022 06:41:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1657633296; 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=LtXyCz0IEfDkRQV6tTiEfKs8tnmrH7wPrOPUpSOgUsI=; b=VYUw4EwWgGlhedwsXNJvIHW8kHuOLJtCiLnBHh4wyDmdMmBL1rq+wcsyAW/VLgYjUCdl25 YGU1dilfjbUNZSJZTiVzbpyWrX4Ac6oCBEFSSkYuMi17fPf8x0iio4xkU/l/wyYSHXza+4 aSwGesKnZaepy0NDgYEUfBTQPBTRkvI= Received: from mail-qv1-f72.google.com (mail-qv1-f72.google.com [209.85.219.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-120-1zJAXwVcN5G0zw5j2GIbQQ-1; Tue, 12 Jul 2022 09:41:35 -0400 X-MC-Unique: 1zJAXwVcN5G0zw5j2GIbQQ-1 Received: by mail-qv1-f72.google.com with SMTP id m11-20020a0cfbab000000b004738181b474so1257439qvp.6 for ; Tue, 12 Jul 2022 06:41:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=LtXyCz0IEfDkRQV6tTiEfKs8tnmrH7wPrOPUpSOgUsI=; b=7K216LMn7SYQdVcnHDQIj42FYeTODGq1lRF/TxsNLAttmCIXCaNRZ67HVTHi23Biwh gCK6YDkGajSYHMJMa9cwLa4B/G+sqq/t9WeRbKCFACvslOEY4Q7oUc/q7LAxikqCuhoG zjF/kmLYEI0nL/jCQFqpVIvyziEAagC3ZkTwqbQWxyrVPH8xLiksA03NIeNUuYdumQUs m9Lg9Ra5XDYbYWebYpKrLv5glZeQbhIoPXms1CTmcFFcUALQQs3BUUlU+Wo/ze4qZPBk DNeKN5uHfqVdZIzbZ4KCrr9WXa9jk/IIMThSPQopR5Ab494bzCNar9TntsFRcUzkfpVT JPXA== X-Gm-Message-State: AJIora9a7fCHNcCj5EDLYXrBilkH0psMABV+RO1u/FCJG6et+79fQxgx mL8sc+yDyDTFLAIMuXiqEpR/PxYlwAw0N6b762Aa35Qtef5uhQPfoHG72qy+QbedAUOS8ODrAUW ip4v1RUkhp+MS44cU/w6cx59w X-Received: by 2002:a05:620a:40cf:b0:6b1:41dd:9710 with SMTP id g15-20020a05620a40cf00b006b141dd9710mr14646817qko.727.1657633294702; Tue, 12 Jul 2022 06:41:34 -0700 (PDT) X-Received: by 2002:a05:620a:40cf:b0:6b1:41dd:9710 with SMTP id g15-20020a05620a40cf00b006b141dd9710mr14646786qko.727.1657633294359; Tue, 12 Jul 2022 06:41:34 -0700 (PDT) Received: from [10.35.4.238] (bzq-82-81-161-50.red.bezeqint.net. [82.81.161.50]) by smtp.gmail.com with ESMTPSA id l10-20020a05620a28ca00b006b59f02224asm2379927qkp.60.2022.07.12.06.41.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Jul 2022 06:41:33 -0700 (PDT) Message-ID: <6dcd11aefcd817ee0f8603328886df3023a98fa5.camel@redhat.com> Subject: Re: [PATCH v3] KVM: x86: Send EOI to SynIC vectors on accelerated EOI-induced VM-Exits From: Maxim Levitsky To: Wang Guangju , seanjc@google.com, pbonzini@redhat.com, vkuznets@redhat.com, jmattson@google.com, wanpengli@tencent.com, bp@alien8.de, joro@8bytes.org, suravee.suthikulpanit@amd.com, hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com, kvm@vger.kernel.org Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, lirongqing@baidu.com Date: Tue, 12 Jul 2022 16:41:28 +0300 In-Reply-To: <20220712123210.89-1-wangguangju@baidu.com> References: <20220712123210.89-1-wangguangju@baidu.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-5.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2022-07-12 at 20:32 +0800, Wang Guangju wrote: > When EOI virtualization is performed on VMX, kvm_apic_set_eoi_accelerated() > is called upon EXIT_REASON_EOI_INDUCED but unlike its non-accelerated > apic_set_eoi() sibling, Hyper-V SINT vectors are left unhandled. > > Send EOI to Hyper-V SINT vectors when handling acclerated EOI-induced > VM-Exits. KVM Hyper-V needs to handle the SINT EOI irrespective of whether > the EOI is acclerated or not. How does this relate to the AutoEOI feature, and the fact that on AVIC, it can't intercept EOI at all (*)? Best regards, Maxim Levitsky (*) AVIC does intercept EOI write but only for level triggered interrupts. > > Rename kvm_apic_set_eoi_accelerated() to kvm_apic_set_eoi() and let the > non-accelerated helper call the "acclerated" version. That will document > the delta between the non-accelerated path and the accelerated path. > In addition, guarantee to trace even if there's no valid vector to EOI in > the non-accelerated path in order to keep the semantics of the function > intact. > > Fixes: 5c919412fe61 ("kvm/x86: Hyper-V synthetic interrupt controller") > Cc: > Tested-by: Wang Guangju > Suggested-by: Sean Christopherson > Suggested-by: Vitaly Kuznetsov > Co-developed-by: Li Rongqing > Signed-off-by: Wang Guangju > --- >  v1 -> v2: Updated the commit message and implement a new inline function >  of apic_set_eoi_vector() > >  v2 -> v3: Updated the subject and commit message, drop func >  apic_set_eoi_vector() and rename kvm_apic_set_eoi_accelerated() >  to kvm_apic_set_eoi() > >  arch/x86/kvm/lapic.c   | 45 ++++++++++++++++++++++----------------------- >  arch/x86/kvm/lapic.h   |  2 +- >  arch/x86/kvm/vmx/vmx.c |  3 ++- >  3 files changed, 25 insertions(+), 25 deletions(-) > > diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c > index f03facc..b2e72ab 100644 > --- a/arch/x86/kvm/lapic.c > +++ b/arch/x86/kvm/lapic.c > @@ -1269,46 +1269,45 @@ static void kvm_ioapic_send_eoi(struct kvm_lapic *apic, int vector) >         kvm_ioapic_update_eoi(apic->vcpu, vector, trigger_mode); >  } >   > +/* > + * Send EOI for a valid vector.  The caller, or hardware when this is invoked > + * after an accelerated EOI VM-Exit, is responsible for updating the vISR and > + * vPPR. > + */ > +void kvm_apic_set_eoi(struct kvm_lapic *apic, int vector) > +{ > +       trace_kvm_eoi(apic, vector); > + > +       if (to_hv_vcpu(apic->vcpu) && > +           test_bit(vector, to_hv_synic(apic->vcpu)->vec_bitmap)) > +               kvm_hv_synic_send_eoi(apic->vcpu, vector); > + > +       kvm_ioapic_send_eoi(apic, vector); > +       kvm_make_request(KVM_REQ_EVENT, apic->vcpu); > +} > +EXPORT_SYMBOL_GPL(kvm_apic_set_eoi); > + >  static int apic_set_eoi(struct kvm_lapic *apic) >  { >         int vector = apic_find_highest_isr(apic); >   > -       trace_kvm_eoi(apic, vector); > - >         /* >          * Not every write EOI will has corresponding ISR, >          * one example is when Kernel check timer on setup_IO_APIC >          */ > -       if (vector == -1) > +       if (vector == -1) { > +               trace_kvm_eoi(apic, vector); >                 return vector; > +       } >   >         apic_clear_isr(vector, apic); >         apic_update_ppr(apic); >   > -       if (to_hv_vcpu(apic->vcpu) && > -           test_bit(vector, to_hv_synic(apic->vcpu)->vec_bitmap)) > -               kvm_hv_synic_send_eoi(apic->vcpu, vector); > +       kvm_apic_set_eoi(apic, vector); >   > -       kvm_ioapic_send_eoi(apic, vector); > -       kvm_make_request(KVM_REQ_EVENT, apic->vcpu); >         return vector; >  } >   > -/* > - * this interface assumes a trap-like exit, which has already finished > - * desired side effect including vISR and vPPR update. > - */ > -void kvm_apic_set_eoi_accelerated(struct kvm_vcpu *vcpu, int vector) > -{ > -       struct kvm_lapic *apic = vcpu->arch.apic; > - > -       trace_kvm_eoi(apic, vector); > - > -       kvm_ioapic_send_eoi(apic, vector); > -       kvm_make_request(KVM_REQ_EVENT, apic->vcpu); > -} > -EXPORT_SYMBOL_GPL(kvm_apic_set_eoi_accelerated); > - >  void kvm_apic_send_ipi(struct kvm_lapic *apic, u32 icr_low, u32 icr_high) >  { >         struct kvm_lapic_irq irq; > diff --git a/arch/x86/kvm/lapic.h b/arch/x86/kvm/lapic.h > index 762bf61..48260fa 100644 > --- a/arch/x86/kvm/lapic.h > +++ b/arch/x86/kvm/lapic.h > @@ -126,7 +126,7 @@ u64 kvm_get_lapic_tscdeadline_msr(struct kvm_vcpu *vcpu); >  void kvm_set_lapic_tscdeadline_msr(struct kvm_vcpu *vcpu, u64 data); >   >  void kvm_apic_write_nodecode(struct kvm_vcpu *vcpu, u32 offset); > -void kvm_apic_set_eoi_accelerated(struct kvm_vcpu *vcpu, int vector); > +void kvm_apic_set_eoi(struct kvm_lapic *apic, int vector); >   >  int kvm_lapic_set_vapic_addr(struct kvm_vcpu *vcpu, gpa_t vapic_addr); >  void kvm_lapic_sync_from_vapic(struct kvm_vcpu *vcpu); > diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c > index 9258468..f8b9eb1 100644 > --- a/arch/x86/kvm/vmx/vmx.c > +++ b/arch/x86/kvm/vmx/vmx.c > @@ -5519,9 +5519,10 @@ static int handle_apic_eoi_induced(struct kvm_vcpu *vcpu) >  { >         unsigned long exit_qualification = vmx_get_exit_qual(vcpu); >         int vector = exit_qualification & 0xff; > +       struct kvm_lapic *apic = vcpu->arch.apic; >   >         /* EOI-induced VM exit is trap-like and thus no need to adjust IP */ > -       kvm_apic_set_eoi_accelerated(vcpu, vector); > +       kvm_apic_set_eoi(apic, vector); >         return 1; >  } >