X-Received: by 2002:a17:90b:164f:b0:1b9:19de:ef67 with SMTP id il15-20020a17090b164f00b001b919deef67mr2165387pjb.101.1645503218517; Mon, 21 Feb 2022 20:13:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645503218; cv=none; d=google.com; s=arc-20160816; b=Dh1EyT7UkNnG9J0yUrpfBiUqlbr0Rs7ACmWfs8jKGsc/xs1hYqrzO/q0pO2EeRHQ++ 81TD0i0oGk5ztXD8IjPGgnyazbURl94oPo+SEhiTFNIMiII8dM0aGXKd8BeuDYM1zWW2 Ry1lboljArz5jFh/8HTn88K6eFrCV/ffBvcI9xiKFa5Rovgg9blCZkTNlcj3MheVCe89 IRrTpxWKaZBylXLbpEJEf/LqCUZEFR15k+9r6wz62kn+8VDuVwZvEe+Z6irXmvKR1Umr /ISI3XhHOty6I+67Q3g6SKx3oNRzz86wlbY9Pw8sxpIMbGBAc1tHXuLDEUWhk7nr39Q5 7/6A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=zwX/iVI1alQtsPS+zY1FE7ZiDOoWe3bToC+jQ7M1MxQ=; b=u0fkdguMqzgs7PGricEGRdKA6SXqm0pQPiVvHLcYhUt3JF42HbgYFcz0xFGUVyvXsD cRNQX+n24o8G8iyKVlc76MDJjMIzXYNr7qUzx+S1/7JDvymLUqLrNE+F/IGhQB+1fxBn zpUzSaUnvZsK+xM2bVCCNOGnXfH+rtWex047/nQd0GMyJznhUaqY8Opzyu/TP5GRzA1/ yn00Fg/p6s0mBn3GhenVd6yG+D+gXqzVOE/8y77wUp4kwiqYa9CaoZtUp8USdof8VTgQ fI5pbFG57L47tBVjQx4UqJ11pS/OjHj3HiU0NpNhxKmTP2/Hr7Mc/4+I/Ta+W71WSbkm oOeg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=CPOa7+w+; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id e6si8626687plx.565.2022.02.21.20.13.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 21 Feb 2022 20:13:38 -0800 (PST) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=CPOa7+w+; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 123F97F6D7; Mon, 21 Feb 2022 20:13:28 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239111AbiBVCgI (ORCPT + 99 others); Mon, 21 Feb 2022 21:36:08 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:55000 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232278AbiBVCgG (ORCPT ); Mon, 21 Feb 2022 21:36:06 -0500 Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 581D825C5F; Mon, 21 Feb 2022 18:35:42 -0800 (PST) Received: by mail-io1-xd36.google.com with SMTP id w7so18335415ioj.5; Mon, 21 Feb 2022 18:35:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zwX/iVI1alQtsPS+zY1FE7ZiDOoWe3bToC+jQ7M1MxQ=; b=CPOa7+w+iq9ox2HbHVDsRwFSyoshcqyaH5jQI5vWPCHe1uBnZoUQQlDcPWsBUbfRxM jC5DvljspA/9D/JDUEGklidGFwrD4YUj7xYJHRXXFq4gH9+ARFOtzhoJNxpvW/riNeqa yuHPMbbwrV9yzSJIYuN/QqSR0D7P35zrFx8f+UPswi6gGsvPLzBSBEAbccD8dY7dR4ls YbhF2aUxjczw9LI3sZf2fzJqYYscb3Y7BU8QvdUQjnxTeutKqGAFVeVNwRTN6UL7HIiF yoy7akJFThYqVAMttoCoMDRv/KdPlxamta3/eG+pehY/AEL/54WtL/NiITTYKce7dEkH HNgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zwX/iVI1alQtsPS+zY1FE7ZiDOoWe3bToC+jQ7M1MxQ=; b=8MoNWus/03xU6jc0FlxmvGRNk9Y/AqVEVs6DYMfC4JC9WA2wALMgCQy+Gu96en6cdh ZojU7zsK3UwWBahiu7Se1B2SWLIF8eO3XIZRxHhi/BfSR+xrKCr3aH10OwGyOGtnEsYz 9u9/KiRMX4rYVuXxLoPmYyxK8Xw4MncTzB+/9tuKQ8l3N13kpKIBQJRdH06O/yVKGHvk esDC4RF3YE7oYF6Eybbrp3mYaAwE4DKGyQuuDFKJtQntnmI6EC8pCJZZy1sEujIG/n7Y 2A1MjWfZ6yGsgiQ1BCuab/jYD19fBDbk5bP8hwMk41UPmqzgOOK0da61Ar2hYLkdLFGG abRg== X-Gm-Message-State: AOAM533Ze0+tGrRG/opPrM/vRXuc+kXeq5X8WiNSJiqoai64z0+PyQwX udfL2xEIOLe43mSbHeYnvB6Tvts7shC06rUXEZA= X-Received: by 2002:a02:b048:0:b0:311:85be:a797 with SMTP id q8-20020a02b048000000b0031185bea797mr17100406jah.284.1645497341759; Mon, 21 Feb 2022 18:35:41 -0800 (PST) MIME-Version: 1.0 References: <20220218110547.11249-1-flyingpeng@tencent.com> In-Reply-To: From: Hao Peng Date: Tue, 22 Feb 2022 10:34:21 +0800 Message-ID: Subject: Re: [PATCH] kvm: correct comment description issue To: Sean Christopherson Cc: pbonzini@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no 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 Sat, Feb 19, 2022 at 12:04 AM Sean Christopherson wrote: > > "KVM: VMX:" for the scope. A more specific shortlog would also be helfpul, stating > that a comment is being modified doesn't provide any info about what comment. > > On Fri, Feb 18, 2022, Peng Hao wrote: > > loaded_vmcs does not have this field 'vcpu', modify this comment. > > It would be helpful to state that loaded_vmcs has 'cpu', not 'vcpu'. It's hard to > identify what's being changed. > > > Something like this? > > KVM: VMX: Fix typos above smp_wmb() comment in __loaded_vmcs_clear() > > Fix a comment documenting the memory barrier related to clearing a > loaded_vmcs; loaded_vmcs tracks the host CPU the VMCS is loaded on via > the field 'cpu', it doesn't have a 'vcpu' field. > > With a tweaked shortlog/changelog (doesn't have to be exactly the above), > Thanks for the suggestions for these patches, I will send again. > Reviewed-by: Sean Christopherson > > > Signed-off-by: Peng Hao > > --- > > arch/x86/kvm/vmx/vmx.c | 8 ++++---- > > 1 file changed, 4 insertions(+), 4 deletions(-) > > > > diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c > > index 7dce746c175f..0ffcfe54eea5 100644 > > --- a/arch/x86/kvm/vmx/vmx.c > > +++ b/arch/x86/kvm/vmx/vmx.c > > @@ -644,10 +644,10 @@ static void __loaded_vmcs_clear(void *arg) > > > > /* > > * Ensure all writes to loaded_vmcs, including deleting it from its > > - * current percpu list, complete before setting loaded_vmcs->vcpu to > > - * -1, otherwise a different cpu can see vcpu == -1 first and add > > - * loaded_vmcs to its percpu list before it's deleted from this cpu's > > - * list. Pairs with the smp_rmb() in vmx_vcpu_load_vmcs(). > > + * current percpu list, complete before setting loaded_vmcs->cpu to > > + * -1, otherwise a different cpu can see loaded_vmcs->cpu == -1 first > > + * and add loaded_vmcs to its percpu list before it's deleted from this > > + * cpu's list. Pairs with the smp_rmb() in vmx_vcpu_load_vmcs(). > > */ > > smp_wmb(); > > > > -- > > 2.27.0 > >