From: "Thomson, Jack" <jackabt.amazon@gmail.com>
To: jthoughton@google.com
Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
kernel-patches@amazon.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mamarang@amazon.com,
mancio@amazon.co.uk, mingo@redhat.com, pbonzini@redhat.com,
seanjc@google.com, tglx@kernel.org, x86@kernel.org,
zoumboul@amazon.com
Subject: Re: [RFC] KVM: x86/mmu: Prefetch forward run of pages on TDP page faults
Date: Thu, 27 Aug 2026 14:31:31 +0100 [thread overview]
Message-ID: <41e1eee3-2cbd-46e9-9bce-5246244c5d12@gmail.com> (raw)
In-Reply-To: <CADrL8HU2uoOVsOoxY9Sm2edV5-aXzP8QLL2LPShOF6bASpkfmg@mail.gmail.com>
On Tue, Aug 25, 2026, James Houghton wrote:
> Firecracker might be using async PF; using KVM Userfault basically
> disables async PF.
I've been working on exactly this series [1] on top of your KVM
Userfault series that turns userfault exits into async PFs, with
userspace signalling completion either via ioctl or this idea of an
exitless variant which skips the KVM_RUN round-trip per fault which has
some exciting numbers!
It's running in our CI at the moment, and hoping to publish this as an
RFC soon :)
[1]:
https://github.com/firecracker-microvm/firecracker/tree/feature/secret-hiding/resources/hiding_ci/kernels/6.18-secret-hiding/linux_patches/60-async-pf
--
Thanks,
Jack
next prev parent reply other threads:[~2026-08-27 13:31 UTC|newest]
Thread overview: 13+ 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 14:18 ` sashiko-bot
2026-08-25 15:00 ` Sean Christopherson
2026-08-25 15:54 ` James Houghton
2026-08-27 13:31 ` Thomson, Jack [this message]
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
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=41e1eee3-2cbd-46e9-9bce-5246244c5d12@gmail.com \
--to=jackabt.amazon@gmail.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=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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 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.