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,
Binbin Wu <binbin.wu@linux.intel.com>,
Chao Gao <chao.gao@intel.com>, Jim Mattson <jmattson@google.com>
Subject: Re: [PATCH v7 0/2] KVM: VMX: Workaround VMX preemption timer erratum
Date: Wed, 5 Aug 2026 09:46:13 -0700 [thread overview]
Message-ID: <178594834697.3639604.11123768104931379395.b4-ty@google.com> (raw)
In-Reply-To: <20260731171926.2629627-1-seanjc@google.com>
On Fri, 31 Jul 2026 10:19:24 -0700, Sean Christopherson wrote:
> Due to a widespread Intel erratum (e.g. EMR158), programming the VMX
> preemption timer with certain large values may cause the timer to expire
> earlier than expected. The recommended workaround is to cap the timer value
> to strictly less than 2^25 * CPUID.15H:EBX[31:0] / CPUID.15H:EAX[31:0].
>
> v7:
> - Ensure the timer doesn't exceed the architectural max. [Sashiko]
>
> [...]
Applied to kvm-x86 vmx, thanks!
[1/2] KVM: VMX: Bury all of the VMX preemption timer code under CONFIG_X86_64=y
https://github.com/kvm-x86/linux/commit/d0dea3ed847c
[2/2] KVM: VMX: Cap VMX preemption timer to work around Intel erratum
https://github.com/kvm-x86/linux/commit/0aaedada606a
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2026-08-05 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 17:19 Sean Christopherson
2026-07-31 17:19 ` [PATCH v7 1/2] KVM: VMX: Bury all of the VMX preemption timer code under CONFIG_X86_64=y Sean Christopherson
2026-07-31 17:19 ` [PATCH v7 2/2] KVM: VMX: Cap VMX preemption timer to work around Intel erratum Sean Christopherson
2026-08-05 16:46 ` 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=178594834697.3639604.11123768104931379395.b4-ty@google.com \
--to=seanjc@google.com \
--cc=binbin.wu@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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®