From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] KVM: x86: AVIC vTPR fix for 6.17
Date: Wed, 17 Sep 2025 19:52:56 +0200 [thread overview]
Message-ID: <0d38af14-53b9-489e-bd10-27bb6c7af470@redhat.com> (raw)
In-Reply-To: <20250916003831.630382-1-seanjc@google.com>
On 9/16/25 02:38, Sean Christopherson wrote:
> Please grab a single fix for 6.17. The bug has existed for some time, so it's
> not super critical that it get into 6.17, but it'd be nice to get this on its
> way to LTS kernels sooner than later. Thanks!
>
> The following changes since commit 42a0305ab114975dbad3fe9efea06976dd62d381:
>
> Merge tag 'kvmarm-fixes-6.17-1' of https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD (2025-08-29 12:57:31 -0400)
>
> are available in the Git repository at:
>
> https://github.com/kvm-x86/linux.git tags/kvm-x86-fixes-6.17-rcN
>
> for you to fetch changes up to d02e48830e3fce9701265f6c5a58d9bdaf906a76:
>
> KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active (2025-09-10 12:04:16 -0700)
Pulled, thanks.
Paolo
> ----------------------------------------------------------------
> KVM x86 fix for 6.17-rcN
>
> Sync the vTPR from the local APIC to the VMCB even when AVIC is active, to fix
> a bug where host updates to the vTPR, e.g. via KVM_SET_LAPIC or emulation of a
> guest access, effectively get lost and result in interrupt delivery issues in
> the guest.
>
> ----------------------------------------------------------------
> Maciej S. Szmigiero (1):
> KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active
>
> arch/x86/kvm/svm/svm.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
prev parent reply other threads:[~2025-09-17 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 0:38 [GIT PULL] KVM: x86: AVIC vTPR fix for 6.17 Sean Christopherson
2025-09-17 17:52 ` Paolo Bonzini [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=0d38af14-53b9-489e-bd10-27bb6c7af470@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.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