mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 David Matlack <dmatlack@google.com>
Subject: [PATCH 0/2] KVM: x86/mmu: Clean up hugepage split error handling
Date: Fri, 12 Jul 2024 08:13:33 -0700	[thread overview]
Message-ID: <20240712151335.1242633-1-seanjc@google.com> (raw)

"Fix" an impossible scenario where KVM would install a '0' SPTE instead of
using SHADOW_NONPRESENT_VALUE.  In quotes because (a) there's not truly anything
to fix (the code should never be hit), and (b) bugging the VM doesn't guarantee
KVM won't get confused (though it's still better than installing an empty SPTE).

The main motivation for this is to eliminate installing a '0' SPTE so that
future audits of the MMU don't complain about not using SHADOW_NONPRESENT_VALUE.

Sean Christopherson (2):
  KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE
  KVM: x86/mmu: Clean up make_huge_page_split_spte() definition and
    intro

 arch/x86/kvm/mmu/spte.c | 14 ++++----------
 1 file changed, 4 insertions(+), 10 deletions(-)


base-commit: 771df9ffadb8204e61d3e98f36c5067102aab78f
-- 
2.45.2.993.g49e7a77208-goog


             reply	other threads:[~2024-07-12 15:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 15:13 Sean Christopherson [this message]
2024-07-12 15:13 ` [PATCH 1/2] KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE Sean Christopherson
2024-07-12 15:13 ` [PATCH 2/2] KVM: x86/mmu: Clean up make_huge_page_split_spte() definition and intro Sean Christopherson
2024-07-16 13:57 ` [PATCH 0/2] KVM: x86/mmu: Clean up hugepage split error handling 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=20240712151335.1242633-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=dmatlack@google.com \
    --cc=kvm@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®