From: Sean Christopherson <seanjc@google.com>
To: James Houghton <jthoughton@google.com>
Cc: Marco Marangoni <mamarang@amazon.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-patches@amazon.com" <kernel-patches@amazon.com>,
Riccardo Mancini <mancio@amazon.co.uk>,
Michael Zoumboulakis <zoumboul@amazon.com>,
Marco Marangoni <marco.marangoni@proton.me>
Subject: Re: [RFC] KVM: x86/mmu: Prefetch forward run of pages on TDP page faults
Date: Tue, 25 Aug 2026 14:40:16 -0700 [thread overview]
Message-ID: <ao4LwI2F7jDezZh9@google.com> (raw)
In-Reply-To: <ao4Daj0hnwjP9Lpf@google.com>
On Tue, Aug 25, 2026, Sean Christopherson wrote:
> On Tue, Aug 25, 2026, Sean Christopherson wrote:
> > Somewhat off the cuff and *very* lightly tested, but this seems to do what I want.
> > If it provides comparable performance, I'll write a changelog (or two? e.g. to
> > have direct MMUs switch in a separate patch), and let Sashiko and other bots rip
> > apart my idea.
> >
> > Note! This has a hard dependency on in-flight prefaulting fixes[*]. Without
> > those, prefaulting will hang the vCPU if the root is invalidated.
> > [*] https://lore.kernel.org/all/20260806214050.78058-1-seanjc@google.com
> >
> > Note #2! The below deliberately ignores A/D-disabled MMUs. I can't think of
> > any reason why it matters whether or not KVM can precisely detect accessed SPTEs,
> > all of the aging stuff is already extremely fuzzy.
>
> And of course I posted an untested version (I ripped out the direct MMU prefetching
> as an afterthough, and dropped a printk). This version should actually compile.
This breaks dirty_log_test and dirty_log_page_splitting_test, because KVM creates
writable SPTEs in direct MMUs whenever possible. Because nothing can be simple,
the below in turn breaks pre_fault_memory_test, but I suspect that's a test flaw.
Note, this would also short-circuit async #PF completion when dirty logging is
enabled. I think that's a good thing? If not, we could teach kvm_mmu_do_page_fault()
to differentiate between async #PF and unprompted prefetching.
diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
index 88b6aa1f840f..540d6583995c 100644
--- a/arch/x86/kvm/mmu/mmu.c
+++ b/arch/x86/kvm/mmu/mmu.c
@@ -874,19 +874,11 @@ static void unaccount_nx_huge_page(struct kvm *kvm, struct kvm_mmu_page *sp)
untrack_possible_nx_huge_page(kvm, sp, KVM_SHADOW_MMU);
}
-static struct kvm_memory_slot *gfn_to_memslot_dirty_bitmap(struct kvm_vcpu *vcpu,
- gfn_t gfn,
- bool no_dirty_log)
+static bool kvm_is_memslot_usable_for_prefetch(struct kvm_memory_slot *slot,
+ unsigned int access)
{
- struct kvm_memory_slot *slot;
-
- slot = kvm_vcpu_gfn_to_memslot(vcpu, gfn);
- if (!slot || slot->flags & KVM_MEMSLOT_INVALID)
- return NULL;
- if (no_dirty_log && kvm_slot_dirty_track_enabled(slot))
- return NULL;
-
- return slot;
+ return slot && !(slot->flags & KVM_MEMSLOT_INVALID) &&
+ (!(access & ACC_WRITE_MASK) || !kvm_slot_dirty_track_enabled(slot));
}
/*
@@ -3181,8 +3173,8 @@ static bool kvm_mmu_prefetch_sptes(struct kvm_vcpu *vcpu, gfn_t gfn, u64 *sptep,
if (WARN_ON_ONCE(nr_pages > PTE_PREFETCH_NUM))
return false;
- slot = gfn_to_memslot_dirty_bitmap(vcpu, gfn, access & ACC_WRITE_MASK);
- if (!slot)
+ slot = kvm_vcpu_gfn_to_memslot(vcpu, gfn);
+ if (!kvm_is_memslot_usable_for_prefetch(slot, access))
return false;
nr_pages = kvm_prefetch_pages(slot, gfn, pages, nr_pages);
@@ -4946,6 +4938,8 @@ static int kvm_mmu_do_page_fault(struct kvm_vcpu *vcpu, gpa_t cr2_or_gpa,
*/
fault.gfn = gpa_to_gfn(fault.addr) & ~kvm_gfn_direct_bits(vcpu->kvm);
fault.slot = kvm_vcpu_gfn_to_memslot(vcpu, fault.gfn);
+ if (prefetch && !kvm_is_memslot_usable_for_prefetch(fault.slot, ACC_ALL))
+ return RET_PF_WRITE_PROTECTED;
}
/*
next prev parent reply other threads:[~2026-08-25 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 14:01 [RFC] KVM: x86/mmu: Prefetch forward run of pages on TDP page faults Marco Marangoni
2026-08-25 15:00 ` Sean Christopherson
2026-08-25 15:54 ` James Houghton
2026-08-25 15:59 ` James Houghton
2026-08-25 17:38 ` Marangoni, Marco
2026-08-25 18:06 ` James Houghton
2026-08-25 20:55 ` Marangoni, Marco
2026-08-25 21:01 ` Sean Christopherson
2026-08-25 21:04 ` Sean Christopherson
2026-08-25 21:40 ` Sean Christopherson [this message]
2026-08-25 22:33 ` Marangoni, Marco
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=ao4LwI2F7jDezZh9@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jthoughton@google.com \
--cc=kernel-patches@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mamarang@amazon.com \
--cc=mancio@amazon.co.uk \
--cc=marco.marangoni@proton.me \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
--cc=zoumboul@amazon.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