Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EBF1FC636D6 for ; Wed, 22 Feb 2023 18:39:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232431AbjBVSjf (ORCPT ); Wed, 22 Feb 2023 13:39:35 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42442 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229672AbjBVSjc (ORCPT ); Wed, 22 Feb 2023 13:39:32 -0500 Received: from mail-pl1-x64a.google.com (mail-pl1-x64a.google.com [IPv6:2607:f8b0:4864:20::64a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EC54C2E0F3 for ; Wed, 22 Feb 2023 10:39:31 -0800 (PST) Received: by mail-pl1-x64a.google.com with SMTP id j10-20020a170902da8a00b00188cd4769bcso3944215plx.0 for ; Wed, 22 Feb 2023 10:39:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=1RX0usnmg54lDWkRfTdJaybq9v0ennM6mLW3m9XCSVk=; b=dHlkLbxj7oVZhPWN9VK1XIGSE8j9w1WDljtOSlDVt0y057HlUP4h9F4yHngWwJPkEj PQqTGNrD2PFs6kuiihbTD8ypAtiBfXtIYUC8xgr6U18lwjwCnEvxUMlfAePYGGGLI9A8 1Q9WU0wrrMXDWaDWm2Hvg5VrtzNmd4yZuFidDo8W4BXxwr3hGy/Av0/Nh/wxUMMfwNrx zGImFPOF0jQxK93E4SD0QlQXEHMaVl7i5PS0X06BUBNKLKtRsQTmMYdfNwP78VdeVDTH bMW0RQCBXgGFEA+L+of+7fo6IYkvZOtkkKi77r8ichXwD9vOQneqon/YxKD/jreYm6Da D5XQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=1RX0usnmg54lDWkRfTdJaybq9v0ennM6mLW3m9XCSVk=; b=VjZcomtkGrpzNOB+T0FrashnkeK8Sl66FDOYKfacam1woBrzynI7mosmh3pR4mJixV 7VgUXbhFuOhOodHEAhOLC/gs2OWv/W9TCeMPQ6PXyb+dtmYtuUVDZsh/EBt60M8OwYPF 9nRNRB713mFMf+MjmMZ/Um7RaUuQUiOGGxpF7c6YXZqrmSbspfVv2YQ95/GZY/Qdf1+Q gzFve8ZzTUb+mF5wASuqd1fCdjrpNcuTHupHI2W3AVB8N8XO1mVmAgZofqfzrunkstXp YaKozuIeh/PgBkpzoQh7GLDp7DNbBuGJoVHvAhl2lTOs05p4YuMPl4LYphWanBkiLH4I hpTw== X-Gm-Message-State: AO0yUKWg4SH2dkI5vpXxsl86wBCbWdIFgLj5vmdhLtd0+fJ6JSnMOAlX jLnSG2p3y8G+/bKVGq9lzpmWUNd1kQM= X-Google-Smtp-Source: AK7set+5dRB8iLmwnKzhs7QvBP57/KrG+2y4uCZ7f6ytg7iZfRgE8z0UbaB0ZlzERRTIoeNciM4bw5J7PfU= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a63:3e4f:0:b0:4fc:a80e:e6ec with SMTP id l76-20020a633e4f000000b004fca80ee6ecmr1209989pga.5.1677091171417; Wed, 22 Feb 2023 10:39:31 -0800 (PST) Date: Wed, 22 Feb 2023 10:39:30 -0800 In-Reply-To: <20230220084500.938739-1-jun.miao@intel.com> Mime-Version: 1.0 References: <20230220084500.938739-1-jun.miao@intel.com> Message-ID: Subject: Re: [PATCH] KVM: Align the function name of kvm_swap_active_memslots() From: Sean Christopherson To: Jun Miao Cc: pbonzini@redhat.com, corbet@lwn.net, maciej.szmigiero@oracle.com, kvm@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Nit, "Align" is a confusing because it's often used to refer to indentation. Maybe? KVM: Fix comments that refer to the non-existent install_new_memslots() On Mon, Feb 20, 2023, Jun Miao wrote: > The function of install_new_memslots() is replaced by kvm_swap_active_memslots(). > In order to avoid confusion, align the name in the comments which always be ignored. > > Fixes: a54d806688fe "KVM: Keep memslots in tree-based structures instead of array-based ones") > Signed-off-by: Jun Miao > --- > Documentation/virt/kvm/locking.rst | 2 +- > include/linux/kvm_host.h | 4 ++-- > virt/kvm/kvm_main.c | 4 ++-- > 3 files changed, 5 insertions(+), 5 deletions(-) > > diff --git a/Documentation/virt/kvm/locking.rst b/Documentation/virt/kvm/locking.rst > index 14c4e9fa501d..ac0e549a3ae7 100644 > --- a/Documentation/virt/kvm/locking.rst > +++ b/Documentation/virt/kvm/locking.rst > @@ -21,7 +21,7 @@ The acquisition orders for mutexes are as follows: > - kvm->mn_active_invalidate_count ensures that pairs of > invalidate_range_start() and invalidate_range_end() callbacks > use the same memslots array. kvm->slots_lock and kvm->slots_arch_lock > - are taken on the waiting side in install_new_memslots, so MMU notifiers > + are taken on the waiting side in kvm_swap_active_memslots, so MMU notifiers Can you send a v2 and opportunistically add () to the blurbs that don't have it? I.e. so these are all "kvm_swap_active_memslots()"? Thanks!