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,
	"syzbot ci" <syzbot+ci493c6d734b63e050@syzkaller.appspotmail.com>,
	"Stefano Garzarella" <sgarzare@redhat.com>,
	"Carlos López" <clopez@suse.de>
Subject: [PATCH v3 0/2] KVM: x86: Fix VM-Entry fail due to stale CR8 intercept
Date: Thu, 18 Jun 2026 10:43:45 -0700	[thread overview]
Message-ID: <20260618174347.1981064-1-seanjc@google.com> (raw)

Carlos' fix for a bug where KVM neglects to update TPR_THRESHOLD and runs
afoul of VMX's consistency check that the current TPR won't immediately
generate a VM-Exit.

v3: Call get_vmcs12() iff is_guest_mode() is true to workaround a lockdep
    false positive. [syzbot]

v2:
 - https://lore.kernel.org/all/20260610214523.2905255-2-clopez@suse.de
 - Call kvm_lapic_update_cr8_intercept() from apic_update_ppr() instead
   of issuing KVM_REQ_EVENTS from handle_tpr_below_threshold().

Carlos López (1):
  KVM: x86: Unconditionally recompute CR8 intercept on PPR update

Sean Christopherson (1):
  KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest
    mode

 arch/x86/kvm/lapic.c   | 2 ++
 arch/x86/kvm/vmx/vmx.c | 3 +--
 arch/x86/kvm/x86.c     | 5 +----
 3 files changed, 4 insertions(+), 6 deletions(-)


base-commit: 9d4853b044beefa21c4ee3e18c40653601a64ced
-- 
2.55.0.rc0.738.g0c8ab3ebcc-goog


             reply	other threads:[~2026-06-18 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 17:43 Sean Christopherson [this message]
2026-06-18 17:43 ` [PATCH v3 1/2] KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode Sean Christopherson
2026-06-18 17:43 ` [PATCH v3 2/2] KVM: x86: Unconditionally recompute CR8 intercept on PPR update Sean Christopherson
2026-06-24  9:55 ` [PATCH v3 0/2] KVM: x86: Fix VM-Entry fail due to stale CR8 intercept 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=20260618174347.1981064-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=clopez@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=syzbot+ci493c6d734b63e050@syzkaller.appspotmail.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®