public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Isaku Yamahata <isaku.yamahata@intel.com>
Cc: kvm@vger.kernel.org, isaku.yamahata@gmail.com,
	 Paolo Bonzini <pbonzini@redhat.com>,
	linux-kernel@vger.kernel.org,  rick.p.edgecombe@intel.com
Subject: Re: [PATCH 00/32] KVM: VMX APIC timer virtualization support
Date: Wed, 4 Feb 2026 09:24:47 -0800	[thread overview]
Message-ID: <aYOA303zHQY4CUf1@google.com> (raw)
In-Reply-To: <aYN7s_WTAp9Nr3U6@iyamahat-desk>

On Wed, Feb 04, 2026, Isaku Yamahata wrote:
> On Wed, Feb 04, 2026 at 05:55:50AM -0800,
> Sean Christopherson <seanjc@google.com> wrote:
> 
> > > [1] Intel Architecture Instruction Set Extensions and Future Features
> > > September 2025 319433-059
> > > Chapter 8 APIC-TIMER VIRTUALIZATION
> > > https://cdrdv2.intel.com/v1/dl/getContent/671368
> > 
> > What CPU generation is expected to have APIC-timer virtualization?  DMR?
> 
> CWF.

What P-core CPU generation?  No offence to the Forest family, but I don't think
most people are chomping at the bit to get their hands on CWF :-)

      reply	other threads:[~2026-02-04 17:24 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 18:16 [PATCH 00/32] KVM: VMX APIC timer virtualization support isaku.yamahata
2026-02-03 18:16 ` [PATCH 01/32] KVM: VMX: Detect APIC timer virtualization bit isaku.yamahata
2026-02-03 18:16 ` [PATCH 02/32] KVM: x86: Implement APIC virt timer helpers with callbacks isaku.yamahata
2026-02-03 18:16 ` [PATCH 03/32] KVM: x86/lapic: Start/stop sw/hv timer on vCPU un/block isaku.yamahata
2026-02-03 18:16 ` [PATCH 04/32] KVM: x86/lapic: Wire DEADLINE MSR update to guest virtual TSC deadline isaku.yamahata
2026-02-03 18:16 ` [PATCH 05/32] KVM: x86/lapic: Add a trace point for guest virtual timer isaku.yamahata
2026-02-03 18:16 ` [PATCH 06/32] KVM: VMX: Implement the hooks for VMX guest virtual deadline timer isaku.yamahata
2026-02-03 18:16 ` [PATCH 07/32] KVM: VMX: Update APIC timer virtualization on apicv changed isaku.yamahata
2026-02-03 18:16 ` [PATCH 08/32] KVM: nVMX: Disallow/allow guest APIC timer virtualization switch to/from L2 isaku.yamahata
2026-02-03 18:16 ` [PATCH 09/32] KVM: nVMX: Pass struct msr_data to VMX MSRs emulation isaku.yamahata
2026-02-03 18:16 ` [PATCH 10/32] KVM: nVMX: Supports VMX tertiary controls and GUEST_APIC_TIMER bit isaku.yamahata
2026-02-03 18:16 ` [PATCH 11/32] KVM: nVMX: Add tertiary VM-execution control VMCS support isaku.yamahata
2026-02-05  0:12   ` kernel test robot
2026-02-03 18:16 ` [PATCH 12/32] KVM: nVMX: Update intercept on TSC deadline MSR isaku.yamahata
2026-02-03 18:16 ` [PATCH 13/32] KVM: nVMX: Handle virtual timer vector VMCS field isaku.yamahata
2026-02-03 18:16 ` [PATCH 14/32] KVM: VMX: Make vmx_calc_deadline_l1_to_host() non-static isaku.yamahata
2026-02-03 18:16 ` [PATCH 15/32] KVM: nVMX: Enable guest deadline and its shadow VMCS field isaku.yamahata
2026-02-05  1:35   ` kernel test robot
2026-02-03 18:16 ` [PATCH 16/32] KVM: nVMX: Add VM entry checks related to APIC timer virtualization isaku.yamahata
2026-02-03 18:17 ` [PATCH 17/32] KVM: nVMX: Add check vmread/vmwrite on tertiary control isaku.yamahata
2026-02-03 18:17 ` [PATCH 18/32] KVM: nVMX: Add check VMCS index for guest timer virtualization isaku.yamahata
2026-02-03 18:17 ` [PATCH 19/32] KVM: VMX: Advertise tertiary controls to the user space isaku.yamahata
2026-02-03 18:17 ` [PATCH 20/32] KVM: VMX: dump_vmcs() support the guest virt timer isaku.yamahata
2026-02-03 18:17 ` [PATCH 21/32] KVM: VMX: Enable APIC timer virtualization isaku.yamahata
2026-02-03 18:17 ` [PATCH 22/32] KVM: VMX: Introduce module parameter for APIC virt timer support isaku.yamahata
2026-02-03 18:17 ` [PATCH 23/32] KVM: nVMX: Introduce module parameter for nested APIC timer virtualization isaku.yamahata
2026-02-03 18:17 ` [PATCH 24/32] KVM: selftests: Add a test to measure local timer latency isaku.yamahata
2026-02-03 18:17 ` [PATCH 25/32] KVM: selftests: Add nVMX support to timer_latency test case isaku.yamahata
2026-02-03 18:17 ` [PATCH 26/32] KVM: selftests: Add test for nVMX MSR_IA32_VMX_PROCBASED_CTLS3 isaku.yamahata
2026-02-03 18:17 ` [PATCH 27/32] KVM: selftests: Add test vmx_set_nested_state_test with EVMCS disabled isaku.yamahata
2026-02-03 18:17 ` [PATCH 28/32] KVM: selftests: Add tests nested state of APIC timer virtualization isaku.yamahata
2026-02-03 18:17 ` [PATCH 29/32] KVM: selftests: Add VMCS access test to " isaku.yamahata
2026-02-03 18:17 ` [PATCH 30/32] KVM: selftests: Test cases for L1 " isaku.yamahata
2026-02-03 18:17 ` [PATCH 31/32] KVM: selftests: Add tests for nVMX to vmx_apic_timer_virt isaku.yamahata
2026-02-03 18:17 ` [PATCH 32/32] Documentation: KVM: x86: Update documentation of struct vmcs12 isaku.yamahata
2026-02-04  7:46 ` [syzbot ci] Re: KVM: VMX APIC timer virtualization support syzbot ci
2026-02-07  5:41   ` Isaku Yamahata
2026-02-04 13:55 ` [PATCH 00/32] " Sean Christopherson
2026-02-04 17:02   ` Isaku Yamahata
2026-02-04 17:24     ` 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=aYOA303zHQY4CUf1@google.com \
    --to=seanjc@google.com \
    --cc=isaku.yamahata@gmail.com \
    --cc=isaku.yamahata@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rick.p.edgecombe@intel.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