From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Like Xu <like.xu.linux@gmail.com>
Subject: Re: [GIT PULL] KVM: x86: MMU changes for 6.6
Date: Thu, 31 Aug 2023 10:27:37 -0700 [thread overview]
Message-ID: <ZPDNielH+HOYV89u@google.com> (raw)
In-Reply-To: <20230830000633.3158416-4-seanjc@google.com>
+Like
On Tue, Aug 29, 2023, Sean Christopherson wrote:
> Please pull MMU changes for 6.6, with a healthy dose of KVMGT cleanups mixed in.
> The other highlight is finally purging the old MMU_DEBUG code and replacing it
> with CONFIG_KVM_PROVE_MMU.
>
> All KVMGT patches have been reviewed/acked and tested by KVMGT folks. A *huge*
> thanks to them for all the reviews and testing, and to Yan in particular.
FYI, Like found a brown paper bag bug[*] that causes selftests that move memory
regions to fail when compiled with CONFIG_KVM_EXTERNAL_WRITE_TRACKING=y. I'm
redoing testing today with that forced on, but barring more falling, the fix is:
diff --git a/arch/x86/kvm/mmu/page_track.c b/arch/x86/kvm/mmu/page_track.c
index b5af8249eb09..cfd0b8092d06 100644
--- a/arch/x86/kvm/mmu/page_track.c
+++ b/arch/x86/kvm/mmu/page_track.c
@@ -306,5 +306,5 @@ void kvm_page_track_flush_slot(struct kvm *kvm, struct kvm_memory_slot *slot)
bool kvm_page_track_has_external_user(struct kvm *kvm)
{
- return hlist_empty(&kvm->arch.track_notifier_head.track_notifier_list);
+ return !hlist_empty(&kvm->arch.track_notifier_head.track_notifier_list);
}
[*] https://lkml.kernel.org/r/7a6488f2-fef4-6709-6a95-168b0c034ff4%40gmail.com
next prev parent reply other threads:[~2023-08-31 17:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 0:06 [GIT PULL] KVM: x86 pull requests for 6.6 Sean Christopherson
2023-08-30 0:06 ` [GIT PULL] KVM: Non-x86 changes " Sean Christopherson
2023-08-31 17:20 ` Paolo Bonzini
2023-08-30 0:06 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2023-08-31 17:39 ` Paolo Bonzini
2023-08-31 18:27 ` Sean Christopherson
2023-08-30 0:06 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2023-08-31 17:27 ` Sean Christopherson [this message]
2023-08-31 17:43 ` Paolo Bonzini
2023-09-01 18:43 ` Sean Christopherson
2023-09-01 21:07 ` Paolo Bonzini
2023-09-01 21:49 ` Sean Christopherson
2023-08-30 0:06 ` [GIT PULL] KVM: x86: PMU " Sean Christopherson
2023-08-31 17:31 ` Paolo Bonzini
2023-08-30 0:06 ` [GIT PULL] KVM: x86: Selftests " Sean Christopherson
2023-08-31 17:21 ` Paolo Bonzini
2023-08-30 0:06 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2023-08-30 0:06 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2023-08-31 17:32 ` Paolo Bonzini
2023-08-31 17:30 ` [GIT PULL] KVM: x86 pull requests " Paolo Bonzini
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=ZPDNielH+HOYV89u@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).