The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: FirstName LastName <vannapurve@google.com>
To: seanjc@google.com, pbonzini@redhat.com, dave.hansen@linux.intel.com
Cc: rick.p.edgecombe@intel.com, dapeng1.mi@linux.intel.com,
	mizhang@google.com,  jmattson@google.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	 Vishal Annapurve <vannapurve@google.com>
Subject: [PATCH 0/2] KVM: TDX: Disable PMU virtualization for TDX VMs
Date: Tue,  5 May 2026 01:41:16 +0000	[thread overview]
Message-ID: <20260505014118.3783476-1-vannapurve@google.com> (raw)

From: Vishal Annapurve <vannapurve@google.com>

TDX module virtualizes PMU for TDX VMs [1]. KVM has limited role to play
in virtualizing PMU accesses and needs additional enlightenment to
support all toggles provided by TDX module.

This series disables PMU virtualization within KVM for TDX VMs, which is
a safe bet until the complete set of PMU controls are implemented within KVM.

[1] Section 15.2: https://cdrdv2.intel.com/v1/dl/getContent/733575

Vishal Annapurve (2):
  KVM: x86: Move the default arch state init before vm_init() call
  KVM: TDX: Disable pmu virtualization for TDX VMs

 arch/x86/kvm/vmx/tdx.c |  6 ++++++
 arch/x86/kvm/x86.c     | 10 +++++-----
 2 files changed, 11 insertions(+), 5 deletions(-)

-- 
2.54.0.545.g6539524ca2-goog


             reply	other threads:[~2026-05-05  1:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  1:41 FirstName LastName [this message]
2026-05-05  1:41 ` [PATCH 1/2] KVM: x86: Move the default arch state init before vm_init() call FirstName LastName
2026-05-05  1:41 ` [PATCH 2/2] KVM: TDX: Disable pmu virtualization for TDX VMs FirstName LastName
2026-05-06 23:03   ` Sean Christopherson
2026-05-06 23:39     ` Vishal Annapurve
2026-05-06 23:56     ` Huang, Kai
2026-05-07  0:40       ` Vishal Annapurve
2026-05-07 14:24         ` Sean Christopherson

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=20260505014118.3783476-1-vannapurve@google.com \
    --to=vannapurve@google.com \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mizhang@google.com \
    --cc=pbonzini@redhat.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=seanjc@google.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