From mboxrd@z Thu Jan 1 00:00:00 1970 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 CD2F5C6FD1D for ; Tue, 4 Apr 2023 23:45:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236607AbjDDXpA (ORCPT ); Tue, 4 Apr 2023 19:45:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56978 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236585AbjDDXo6 (ORCPT ); Tue, 4 Apr 2023 19:44:58 -0400 Received: from mail-pg1-x549.google.com (mail-pg1-x549.google.com [IPv6:2607:f8b0:4864:20::549]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 35E823C3F for ; Tue, 4 Apr 2023 16:44:57 -0700 (PDT) Received: by mail-pg1-x549.google.com with SMTP id bc19-20020a656d93000000b005072b17a298so9998772pgb.14 for ; Tue, 04 Apr 2023 16:44:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; t=1680651896; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=0ibOdHcie65TOdaYolqKBeOIOCBN2xnK/lxtHiVLKRg=; b=D0cbfF5463oQYavXBGOPAoU03JWXCv7oA1d9vmwTWLNpGay36PYBPczThyXy+dW4Nm 5GYungSxRRZI7NWFDx4C98Mw11+GGdk1PaOb7SXExT054gGmTNBXDjhc7ueFcPU/C21u Gxu4V7hbV2RWAAaBa7x0XblZU77DqA0yIRuQMv1kRaZK/TVv4dNou9wkvO2sLahvG3oU R9mvDfKdJHeKevkb7ZmrGxtDQKh/pQlunDmx9Rdu5swZ/dxWunViYpzpE/Q3JJQAtCx1 dleYKHRJp9vBz7jewfRxi4e3tCDgtFRvb+GLW6zKC1U+u3kLJULub2/GLeWF9X0cZHLq uTcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680651896; 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=0ibOdHcie65TOdaYolqKBeOIOCBN2xnK/lxtHiVLKRg=; b=a24ltH//sM0A5343V3c3QUnX9U8u90MBhBKzRmylSJE/q+c0tb9mSAU4JFaa44hY11 4veczjKEBrQxVvwjPPx2nR8Gem9KTKxvLOKjC+06PWULQee14U/DHXDRfDxSDE3qLYD+ MKmLAHRL1bgImD92k/4CYKiDMh2FP+3tDr3ruVnZZjKphC56VzcNEjOG9mO6lHGZZJR6 dKuR/XLY84KXfO3Pfl6vwnsiKwDGOmR2+iV+wB/t21ZHGGiodndzb4ZOlSy+NZA7SAeb KNcFIEt7mEnaXczoOlluUBfbL/g+n/gmcycx/4JcR5j7az1nR/lLcLOEq+vrUZsBdeDQ p9sA== X-Gm-Message-State: AAQBX9fNDp4qQweKDN6xhjBkQ61i08Y1H6Ile9lV6kN8hYHZpgSBDx0D TeMNIhEYEEnryS2dGo7xX6/Wzi5rNU0= X-Google-Smtp-Source: AKy350YLVlIy62AHHlHk9c8dIx6+nA/udfMbMlrAGOP5kad5hVmc86bqJBDmiDyKgkfAvnqrVeLhIgRP9a4= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a05:6a00:18a9:b0:625:659e:65c with SMTP id x41-20020a056a0018a900b00625659e065cmr2259311pfh.1.1680651896738; Tue, 04 Apr 2023 16:44:56 -0700 (PDT) Date: Tue, 4 Apr 2023 16:44:36 -0700 In-Reply-To: <20230321220021.2119033-1-seanjc@google.com> Mime-Version: 1.0 References: <20230321220021.2119033-1-seanjc@google.com> X-Mailer: git-send-email 2.40.0.348.gf938b09366-goog Message-ID: <168063705710.272549.18361161670199891767.b4-ty@google.com> Subject: Re: [PATCH v4 00/13] KVM: x86/mmu: Optimize clear dirty log From: Sean Christopherson To: Sean Christopherson , Paolo Bonzini Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Vipin Sharma , David Matlack , Ben Gardon Content-Type: text/plain; charset="utf-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 21 Mar 2023 15:00:08 -0700, Sean Christopherson wrote: > This is a massaged version of Vipin's series to optimize clearing dirty > state in the TDP MMU. It's basically the same as v3, just spread out over > more patches. The only meaningful difference in the end is that > clear_dirty_gfn_range() also gets similar treatment in handling Dirty vs. > Writable logic. > > Vipin, I'm still planning on applying this for 6.4, but the changes ended > up being a wee bit bigger than I'm comfortable making on the fly, thus the > formal posting. > > [...] Applied to kvm-x86 mmu, thanks! [01/13] KVM: x86/mmu: Add a helper function to check if an SPTE needs atomic write https://github.com/kvm-x86/linux/commit/41e07665f1a6 [02/13] KVM: x86/mmu: Use kvm_ad_enabled() to determine if TDP MMU SPTEs need wrprot https://github.com/kvm-x86/linux/commit/5982a5392663 [03/13] KVM: x86/mmu: Consolidate Dirty vs. Writable clearing logic in TDP MMU https://github.com/kvm-x86/linux/commit/697c89bed94e [04/13] KVM: x86/mmu: Atomically clear SPTE dirty state in the clear-dirty-log flow https://github.com/kvm-x86/linux/commit/89c313f20c1e [05/13] KVM: x86/mmu: Drop access tracking checks when clearing TDP MMU dirty bits https://github.com/kvm-x86/linux/commit/cf05e8c7325e [06/13] KVM: x86/mmu: Bypass __handle_changed_spte() when clearing TDP MMU dirty bits https://github.com/kvm-x86/linux/commit/1e0f42985ffa [07/13] KVM: x86/mmu: Remove "record_dirty_log" in __tdp_mmu_set_spte() https://github.com/kvm-x86/linux/commit/e73008705d0c [08/13] KVM: x86/mmu: Clear only A-bit (if enabled) when aging TDP MMU SPTEs https://github.com/kvm-x86/linux/commit/7ee131e3a3c3 [09/13] KVM: x86/mmu: Drop unnecessary dirty log checks when aging TDP MMU SPTEs https://github.com/kvm-x86/linux/commit/6141df067d04 [10/13] KVM: x86/mmu: Bypass __handle_changed_spte() when aging TDP MMU SPTEs https://github.com/kvm-x86/linux/commit/891f11596068 [11/13] KVM: x86/mmu: Remove "record_acc_track" in __tdp_mmu_set_spte() https://github.com/kvm-x86/linux/commit/0b7cc2547d53 [12/13] KVM: x86/mmu: Remove handle_changed_spte_dirty_log() https://github.com/kvm-x86/linux/commit/1f9973456e80 [13/13] KVM: x86/mmu: Merge all handle_changed_pte*() functions https://github.com/kvm-x86/linux/commit/40fa907e5a69 -- https://github.com/kvm-x86/linux/tree/next https://github.com/kvm-x86/linux/tree/fixes