From: Sean Christopherson <seanjc@google.com>
To: Jon Kohler <jon@nutanix.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
jonmkohler@gmail.com, Dongli Zhang <dongli.zhang@oracle.com>,
Chao Gao <chao.gao@intel.com>,
stable@vger.kernel.org,
Gulshan Gabel <gulshan.gabel@nutanix.com>
Subject: Re: [PATCH 6.18.y] KVM: VMX: Update SVI during runtime APICv activation
Date: Fri, 12 Jun 2026 16:58:43 -0700 [thread overview]
Message-ID: <aiydM6OKxEhsGF57@google.com> (raw)
In-Reply-To: <20260612211003.2503400-1-jon@nutanix.com>
On Fri, Jun 12, 2026, Jon Kohler wrote:
> From: Dongli Zhang <dongli.zhang@oracle.com>
>
> commit b2849bec936be642b5420801f902337f2507648e upstream.
...
> Signed-off-by: Dongli Zhang <dongli.zhang@oracle.com>
> Reviewed-by: Chao Gao <chao.gao@intel.com>
> Link: https://patch.msgid.link/20251110063212.34902-1-dongli.zhang@oracle.com
> [sean: call out that SVM writes vmcb01 directly, tweak comment]
> Link: https://patch.msgid.link/20251205231913.441872-2-seanjc@google.com
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> (cherry picked from commit b2849bec936be642b5420801f902337f2507648e)
> Cc: stable@vger.kernel.org # 6.6.x and above
> Cc: Gulshan Gabel <gulshan.gabel@nutanix.com>
> Signed-off-by: Jon Kohler <jon@nutanix.com>
> ---
>
> This issue is pervasive and has been observed in production with QEMU
> as the VMM. One scenario where this occurs is with Windows guests that
> use the AutoEOI feature, which inhibits APICv
> (APICV_INHIBIT_REASON_HYPERV).
Gah, sorry, my bad. I don't know why I didn't tag this for stable@.
Acked-by: Sean Christopherson <seanjc@google.com>
prev parent reply other threads:[~2026-06-12 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 21:10 [PATCH 6.18.y] KVM: VMX: Update SVI during runtime APICv activation Jon Kohler
2026-06-12 23:58 ` 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=aiydM6OKxEhsGF57@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dongli.zhang@oracle.com \
--cc=gulshan.gabel@nutanix.com \
--cc=hpa@zytor.com \
--cc=jon@nutanix.com \
--cc=jonmkohler@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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