From: Sean Christopherson <seanjc@google.com>
To: David Matlack <dmatlack@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Ben Gardon <bgardon@google.com>,
kvm@vger.kernel.org, Vipin Sharma <vipinsh@google.com>
Subject: Re: [PATCH 0/3] KVM: Performance and correctness fixes for CLEAR_DIRTY_LOG
Date: Tue, 7 Nov 2023 16:05:09 -0800 [thread overview]
Message-ID: <ZUrQtbjLNOxsqpzf@google.com> (raw)
In-Reply-To: <20231027172640.2335197-1-dmatlack@google.com>
On Fri, Oct 27, 2023, David Matlack wrote:
> This series reduces the impact of CLEAR_DIRTY_LOG on guest performance
> (Patch 3) and fixes 2 minor bugs found along the way (Patches 1 and 2).
> David Matlack (3):
> KVM: x86/mmu: Fix off-by-1 when splitting huge pages during CLEAR
> KVM: x86/mmu: Check for leaf SPTE when clearing dirty bit in the TDP
> MMU
> KVM: Aggressively drop and reacquire mmu_lock during CLEAR_DIRTY_LOG
Is there an actual dependency between 1-2 and 3? AFAICT, no? I ask because I
can take the first two as soon as -rc1 is out, but the generic change definitely
needs testing and acks from other architectures.
next prev parent reply other threads:[~2023-11-08 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 17:26 [PATCH 0/3] KVM: Performance and correctness fixes for CLEAR_DIRTY_LOG David Matlack
2023-10-27 17:26 ` [PATCH 1/3] KVM: x86/mmu: Fix off-by-1 when splitting huge pages during CLEAR David Matlack
2023-10-27 17:26 ` [PATCH 2/3] KVM: x86/mmu: Check for leaf SPTE when clearing dirty bit in the TDP MMU David Matlack
2023-10-27 17:26 ` [PATCH 3/3] KVM: Aggressively drop and reacquire mmu_lock during CLEAR_DIRTY_LOG David Matlack
2023-11-08 0:05 ` Sean Christopherson [this message]
2023-11-08 0:23 ` [PATCH 0/3] KVM: Performance and correctness fixes for CLEAR_DIRTY_LOG David Matlack
2023-12-01 1:52 ` Sean Christopherson
2023-12-01 15:59 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZUrQtbjLNOxsqpzf@google.com \
--to=seanjc@google.com \
--cc=bgardon@google.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vipinsh@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.