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;
MIME-Version: 1.0
References: <20230321220021.2119033-1-seanjc@google.com>
In-Reply-To: <20230321220021.2119033-1-seanjc@google.com>
From:   Vipin Sharma <vipinsh@google.com>
Date:   Thu, 30 Mar 2023 17:13:46 -0700
Message-ID: <CAHVum0dV+fjgK-3mcABKACJQrTYNLjaYj-euV4+T6PrFGGd0OA@mail.gmail.com>
Subject: Re: [PATCH v4 00/13] KVM: x86/mmu: Optimize clear dirty log
To:     Sean Christopherson <seanjc@google.com>
Cc:     Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org,
        linux-kernel@vger.kernel.org, David Matlack <dmatlack@google.com>,
        Ben Gardon <bgardon@google.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Tue, Mar 21, 2023 at 3:00=E2=80=AFPM Sean Christopherson <seanjc@google.=
com> 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 ove=
r
> 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 th=
e
> formal posting.
>

Changes look good to me and verified by running perf test also that
the improvement is still similar to previous version. Thanks for the
v4 work.