From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: "Denis V. Lunev" <den@openvz.org>,
devel@openvz.org, Konstantin Khorenko <khorenko@virtuozzo.com>
Subject: Re: [Devel] [PATCH hci-8.1 v2 0/2] KVM: VMX: fix stale SVI after APICv is re-activated at runtime
Date: Thu, 24 Sep 2026 19:24:41 +0200 [thread overview]
Message-ID: <179027068158.3234154.14498888885891618531.b4-ty@b4> (raw)
In-Reply-To: <20260924-b4-prep-kvm-v2-0-ad742e43266c@virtuozzo.com>
On Thu, 24 Sep 2026 19:15:36 +0200, Konstantin Khorenko wrote:
> KVM: VMX: fix stale SVI after APICv is re-activated at runtime
>
> A Windows guest with Hyper-V SynIC enlightenments runs with APICv
> inhibited for as long as Windows uses SynIC auto-EOI. A system_reset
> clears SynIC, the inhibit lifts and KVM re-activates APICv on every
> vCPU. __kvm_vcpu_update_apicv() refreshes the VMCS exec controls but
> never re-syncs GUEST_INTR_STATUS.SVI from the software vISR, so each
> vCPU carries whatever SVI it had when APICv was last switched off.
>
> [...]
Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.3.vz10, thanks!
[1/2] ms/KVM: VMX: Update SVI during runtime APICv activation
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/0571a0e123ea
[2/2] ms/KVM: nVMX: Immediately refresh APICv controls as needed on nested VM-Exit
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/510fb493f8a3
--
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-09-24 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 17:15 Konstantin Khorenko
2026-09-24 17:15 ` [Devel] [PATCH hci-8.1 v2 1/2] ms/KVM: VMX: Update SVI during runtime APICv activation Konstantin Khorenko
2026-09-24 17:15 ` [Devel] [PATCH hci-8.1 v2 2/2] ms/KVM: nVMX: Immediately refresh APICv controls as needed on nested VM-Exit Konstantin Khorenko
2026-09-24 17:24 ` Konstantin Khorenko [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=179027068158.3234154.14498888885891618531.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=den@openvz.org \
--cc=devel@openvz.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.