From: Chao Gao <chao.gao@intel.com>
To: Jim Mattson <jmattson@google.com>
Cc: Sean Christopherson <seanjc@google.com>,
Reinette Chatre <reinette.chatre@intel.com>,
<isaku.yamahata@intel.com>, <pbonzini@redhat.com>,
<erdemaktas@google.com>, <vkuznets@redhat.com>,
<vannapurve@google.com>, <mlevitsk@redhat.com>,
<xiaoyao.li@intel.com>, <rick.p.edgecombe@intel.com>,
<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<chenyi.qiang@intel.com>, Yosry Ahmed <yosry@kernel.org>
Subject: Re: VMX Preemption Timer appears to be buggy on SKX, CLX, and ICX
Date: Mon, 20 Jul 2026 18:03:44 +0800 [thread overview]
Message-ID: <al3ygBbMHq2ltdYN@intel.com> (raw)
In-Reply-To: <CALMp9eQYc0AGjuVqCHL-GGe2cLOCnYZhTso=50HihdxTmNShWw@mail.gmail.com>
On Fri, Jun 12, 2026 at 03:51:56PM -0700, Jim Mattson wrote:
>On Thu, Jun 4, 2026 at 10:56 PM Chao Gao <chao.gao@intel.com> wrote:
>>
>> On Thu, Jun 04, 2026 at 10:34:40PM -0700, Jim Mattson wrote:
>...
>> >With respect to EMR, you wrote previously, "A mitigation for this
>> >erratum is for software to program the VMX preemption timer for values
>> >below 2^25 * CPUID.15H:EBX[31:0] / CPUID.15H:EAX[31:0]."
>> >
>> >My question is whether the exponent, 25, is a fixed value for all
>> >CPUs, regardless of their IA32_VMX_MISC[4:0]. It sounds like you are
>> >saying that the exponent may depend on IA32_VMX_MISC[4:0].
>>
>> Let me double-check this with the internal team and get back to you.
>
>Have you discovered anything?
I just got the final answer:
2^25*M/N is the max value of VMX preemption timer for _all_ affected
processors. Our expectation is that for processors that have different
value it will have the issue fixed (VMX preemption timer will implement
full 32-bit). Use of 2^25*M/N will still be fine.
where M is CPUID.15H:EBX[31:0] and N is CPUID.15H:EAX[31:0].
next prev parent reply other threads:[~2026-07-20 10:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 18:16 [PATCH V9 0/2] KVM: x86: Make bus clock frequency for vAPIC timer configurable Reinette Chatre
2024-06-12 18:16 ` [PATCH V9 1/2] KVM: selftests: Add x86_64 guest udelay() utility Reinette Chatre
2024-06-28 22:46 ` Sean Christopherson
2024-06-12 18:16 ` [PATCH V9 2/2] KVM: selftests: Add test for configure of x86 APIC bus frequency Reinette Chatre
2024-06-28 22:50 ` Sean Christopherson
2024-06-29 0:39 ` VMX Preemption Timer appears to be buggy on SKX, CLX, and ICX Sean Christopherson
2024-07-03 20:14 ` Reinette Chatre
2024-07-03 21:37 ` Reinette Chatre
2024-07-08 5:55 ` Yuan Yao
2026-05-13 1:31 ` Chao Gao
2026-05-14 21:09 ` Sean Christopherson
2026-05-15 6:34 ` Chao Gao
2026-06-04 5:09 ` Jim Mattson
2026-06-04 19:58 ` Sean Christopherson
2026-06-04 21:59 ` Jim Mattson
2026-06-05 2:56 ` Chao Gao
2026-06-05 5:34 ` Jim Mattson
2026-06-05 5:56 ` Chao Gao
2026-06-12 22:51 ` Jim Mattson
2026-06-13 3:03 ` Xiaoyao Li
2026-07-20 10:03 ` Chao Gao [this message]
2026-07-20 17:35 ` Jim Mattson
2024-06-28 22:55 ` [PATCH V9 0/2] KVM: x86: Make bus clock frequency for vAPIC timer configurable Sean Christopherson
2024-06-29 0:10 ` Reinette Chatre
2024-07-10 15:42 ` Sean Christopherson
2024-07-10 17:14 ` Reinette Chatre
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=al3ygBbMHq2ltdYN@intel.com \
--to=chao.gao@intel.com \
--cc=chenyi.qiang@intel.com \
--cc=erdemaktas@google.com \
--cc=isaku.yamahata@intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=vannapurve@google.com \
--cc=vkuznets@redhat.com \
--cc=xiaoyao.li@intel.com \
--cc=yosry@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.