From: Sean Christopherson <seanjc@google.com>
To: "Carlos López" <clopez@suse.de>
Cc: stable@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 6.18.y 0/3] KVM: x86: Backports for VM entry failure due to stale CR8 intercept
Date: Thu, 9 Jul 2026 07:28:26 -0700 [thread overview]
Message-ID: <ak-wCrZ0J-s0d27A@google.com> (raw)
In-Reply-To: <20260709072247.3305784-2-clopez@suse.de>
On Thu, Jul 09, 2026, Carlos López wrote:
> Backport for bb365a506b1e ("KVM: x86: Unconditionally recompute CR8
> intercept on PPR update") with two prerequisite patches.
>
> Resend: fix destination emails (did not properly send first version to
> stable@)
>
> Carlos López (1):
> KVM: x86: Unconditionally recompute CR8 intercept on PPR update
>
> Sean Christopherson (2):
> KVM: x86: Move update_cr8_intercept() to lapic.c
> KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest
> mode
Acked-by: Sean Christopherson <seanjc@google.com>
prev parent reply other threads:[~2026-07-09 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 7:22 [PATCH RESEND 6.18.y 0/3] KVM: x86: Backports for VM entry failure due to stale CR8 intercept Carlos López
2026-07-09 7:22 ` [PATCH RESEND 6.18.y 1/3] KVM: x86: Move update_cr8_intercept() to lapic.c Carlos López
2026-07-09 7:22 ` [PATCH RESEND 6.18.y 2/3] KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode Carlos López
2026-07-09 7:22 ` [PATCH RESEND 6.18.y 3/3] KVM: x86: Unconditionally recompute CR8 intercept on PPR update Carlos López
2026-07-09 13:04 ` [PATCH RESEND 6.18.y 0/3] KVM: x86: Backports for VM entry failure due to stale CR8 intercept Greg KH
2026-07-09 14:28 ` Sean Christopherson [this message]
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=ak-wCrZ0J-s0d27A@google.com \
--to=seanjc@google.com \
--cc=clopez@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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 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.