Received: by 2002:a05:6358:489b:b0:bb:da1:e618 with SMTP id x27csp7591440rwn; Wed, 14 Sep 2022 00:51:53 -0700 (PDT) X-Google-Smtp-Source: AA6agR5r63MyoXYqnkjwTsbpK1eBnK5IGwVFcSwvWzvKJ6qZYeQGMr3qBid1OCfBrHLaHLllcsLz X-Received: by 2002:a63:cc4a:0:b0:439:1c48:2fed with SMTP id q10-20020a63cc4a000000b004391c482fedmr9731949pgi.618.1663141913602; Wed, 14 Sep 2022 00:51:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663141913; cv=none; d=google.com; s=arc-20160816; b=nkBwvWYDp6dCJKDPDxpEHFhetuLnPBbx8lB9RGPlV1fB8JicYdwjnFj65+t3N/+GmE WNz+HvEKR0tTgm7qAryxKPYaIN+ody44gYbUFxQIEUh+BgqfHLdAcKsFO4d1D30GY/iB Uk8YaN98j8D6ZkyJWHY9NEmcu+kTBejRSxZhilxYAhq44DTLBggny9BVnemEfHEt09OA RjrGtb6/Q7MylDbJSMabWHL6769QA9XvUoiMC1czqJ/PQsLxCytqx7fGz5LJT2QPfCgB 7w9eF3Hwpbf8C9zm2lz0Abhe5f7WdUS/cnH5rL/xmJMu9irsWwhoJO5cIzcerBT2EqUN wTGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=c5ZYpTByncp5HN1cWQAD3FaVVr7mGXVV2XjTzUESKj0=; b=dSHuxSct68I0dJVCa7YRTCMzDZ6jVajdIdcPRmOjjcPNv3F16ejGVpihENBjDECkoT 2h0Q7IxuQcGI+YrL7Gqcdz/T69R5nzKoo/H+y+RxKfU393Q9QhNCw3DQtYttjLyz3/YN M57viLPf0h90MztCFlQ3mUzDnhIn71x4u/Mc3Ylk0fAgcsr8OAvMwvq6au+8N+1aOU0G OU/hse0xHz+dqq4F+5qvqVKnEM22SUm3Iek+rpWV2RwGrFXX38HJDeJ5VzFNF12oVHyX 8qXPBmb3OZtYziT7FpW1YmlnPYtYK/2Wk7PcG507UY1ua9RtEflRiBV8ThB0zrOz2A9v ykRg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=BxaLnc1M; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k18-20020a170902ce1200b00178264b1c03si11341517plg.395.2022.09.14.00.51.41; Wed, 14 Sep 2022 00:51:53 -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=@google.com header.s=20210112 header.b=BxaLnc1M; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229719AbiINHmk (ORCPT + 99 others); Wed, 14 Sep 2022 03:42:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41216 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229484AbiINHmi (ORCPT ); Wed, 14 Sep 2022 03:42:38 -0400 Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E458C7287F for ; Wed, 14 Sep 2022 00:42:37 -0700 (PDT) Received: by mail-pl1-x62e.google.com with SMTP id f24so14298948plr.1 for ; Wed, 14 Sep 2022 00:42:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=c5ZYpTByncp5HN1cWQAD3FaVVr7mGXVV2XjTzUESKj0=; b=BxaLnc1MXY1pE93RhGGQ/rxkxCg6rVjgniDvBvWlyWMsWQ/WkY0SZn2Dcd4Z8O9fQx 6WmxkwHh9sTJhHUuIXfiAqjBRVo8WAH+p1Ebmmewwt43D2CB+WjtwYDMgc7UBFUANuG7 IcoXy4jVuT9Xctl0icw8j9nU3ZaRKasYOKTIobMTWuws1M4lLhPquYty+k3tbkAER6C0 nAEdV24vO3920A4s8cQa19MoTnddBoWWP8ZQwqnwlgTuYxa1cUj8GnSYh1dawQSp7/4e 6EkjwQaJuRbLqQPN/TxkrVwhaOn3xnIGI5M2FSF1oKD1mLpgFPNjFTWR1XI08g9tVUa2 c1NA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=c5ZYpTByncp5HN1cWQAD3FaVVr7mGXVV2XjTzUESKj0=; b=xYnOsepjBCBaoAcaf93f6g/4HAKOEE2RtyS4l0GrLFnqZeZwA2THGAV8uW5Sg/QBlb kQHpdJhEloyWoJXYXb+IMISG9jUvr1seMylnKg0YwmKU10NqMcdCN2I0c7GIlO4+3/2h UZiHqhNlkyHOyrXzWXDdhF+Ga5ozjIJ8IaCTFzVxcEx5jTli9HkUzPxVvI+ReNgYEIXr vptd65NHLBnv/cvmaTuY3Yr+OCdDLrifEW8N7VVuGFGk1c4EFZOWeu1mgjr/9l+l5CpK yEIKLZ0iA+xWweks5RF68HidP/PpP6oZ4QCMj9b5pYi8jvRb54+bHr3e2WdXyOhiOJkx 6vAw== X-Gm-Message-State: ACgBeo1bR7+uG5pVM0oISJ40dN+raEeOn6quiHZSn+yCP67aknxzlQw2 J+ug5d7uGkH1WVd5cOvlxEqhHQ== X-Received: by 2002:a17:902:ccc7:b0:16c:484f:4c69 with SMTP id z7-20020a170902ccc700b0016c484f4c69mr36564183ple.118.1663141356949; Wed, 14 Sep 2022 00:42:36 -0700 (PDT) Received: from google.com (7.104.168.34.bc.googleusercontent.com. [34.168.104.7]) by smtp.gmail.com with ESMTPSA id m6-20020a17090a2c0600b001faf7a88138sm8368043pjd.42.2022.09.14.00.42.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 14 Sep 2022 00:42:36 -0700 (PDT) Date: Wed, 14 Sep 2022 07:42:33 +0000 From: Sean Christopherson To: "Suthikulpanit, Suravee" Cc: Paolo Bonzini , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Maxim Levitsky , Li RongQing Subject: Re: [PATCH v2 13/23] KVM: x86: Disable APIC logical map if vCPUs are aliased in logical mode Message-ID: References: <20220903002254.2411750-1-seanjc@google.com> <20220903002254.2411750-14-seanjc@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL autolearn=ham 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, Sep 13, 2022, Suthikulpanit, Suravee wrote: > Hi Sean > > On 9/2/2022 7:22 PM, Sean Christopherson wrote: > > Disable the optimized APIC logical map if multiple vCPUs are aliased to > > the same logical ID. Architecturally, all CPUs whose logical ID matches > > the MDA are supposed to receive the interrupt; overwriting existing map > > entries can result in missed IPIs. > > > > Fixes: 1e08ec4a130e ("KVM: optimize apic interrupt delivery") > > Signed-off-by: Sean Christopherson > > Reviewed-by: Maxim Levitsky > > --- > > arch/x86/kvm/lapic.c | 5 +++-- > > 1 file changed, 3 insertions(+), 2 deletions(-) > > > > diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c > > index 6b2f538b8fd0..75748c380ceb 100644 > > --- a/arch/x86/kvm/lapic.c > > +++ b/arch/x86/kvm/lapic.c > > @@ -303,12 +303,13 @@ void kvm_recalculate_apic_map(struct kvm *kvm) > > if (!mask) > > continue; > > - if (!is_power_of_2(mask)) { > > + ldr = ffs(mask) - 1; > > + if (!is_power_of_2(mask) || cluster[ldr]) { > > Should this be checking if the cluster[ldr] is pointing to the same struct > apic instead? For example: > > if (!is_power_of_2(mask) || cluster[ldr] != apic) > > From my observation, the kvm_recalculate_apic_map() can be called many > times, and the cluster[ldr] could have already been assigned from the > previous invocation. So, as long as it is the same, it should be okay. No, because cluster[ldr] can never match "apic". kvm_recalculate_apic_map() creates and populates a _new_ kvm_apic_map every time, it doesn't do an in-place update of the current map. The loop containing this code is: kvm_for_each_vcpu(i, vcpu, kvm) { struct kvm_lapic *apic = vcpu->arch.apic; ... } so it's impossible for cluster[ldr] to hold the current "apic", because this is the first and only iteration that processes the current "apic".