mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Sashiko Bot <sashiko-bot@kernel.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	 Naveen N Rao <naveen@kernel.org>,
	Alexandru Elisei <alexandru.elisei@arm.com>
Subject: [PATCH v4 0/2] KVM: Skip mmu_notifier invalidations for gmem-only slots
Date: Mon, 16 Nov 2026 17:15:11 -0800	[thread overview]
Message-ID: <20261117011513.39419-1-seanjc@google.com> (raw)

Fix a lurking bug where KVM incorrectly prefetches SPTEs for gmem-only memslots
using fast GUP, i.e. VMAs, and then skip mmu_notifier invalidations for
gmem-only memslots (because as the name suggests, KVM MMUs are supposed to
only get PFNs for gmem-only memslots straight from guest_memfd).

v4:
 - Tack on a patch to disallow prefetching gmem-only memslots using a VMA.
   [Sashiko, Lorenzo]

v3:
 - https://lore.kernel.org/all/20261113164000.467175-1-seanjc@google.com
 - v1, but with a different changelog.

v2: https://lore.kernel.org/all/20260714160411.302386-1-alexandru.elisei@arm.com

v1: https://lore.kernel.org/all/20260615155244.183044-1-alexandru.elisei@arm.com

Alexandru Elisei (1):
  KVM: Skip gfn-based MMU notifier invalidations for guest_memfd-only
    memslots

Sean Christopherson (1):
  KVM: Disallow prefetching PFNs (for SPTEs) via VMAs for gmem-only
    memslots

 virt/kvm/kvm_main.c | 7 +++++++
 1 file changed, 7 insertions(+)


base-commit: d21eef2084a9af87ac2a783bc7c2b175ba114e4e
-- 
2.56.1.703.gf848ed807c-goog


             reply	other threads:[~2026-11-17  1:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17  1:15 Sean Christopherson [this message]
2026-11-17  1:15 ` [PATCH v4 1/2] KVM: Disallow prefetching PFNs (for SPTEs) via VMAs for gmem-only memslots Sean Christopherson
2026-11-17  1:15 ` [PATCH v4 2/2] KVM: Skip gfn-based MMU notifier invalidations for guest_memfd-only memslots 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=20261117011513.39419-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=alexandru.elisei@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=naveen@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sashiko-bot@kernel.org \
    /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

all inboxes | Powered by JetHome®