From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: x86: TDX fixes for 6.16-rc7
Date: Thu, 17 Jul 2025 07:52:16 -0700 [thread overview]
Message-ID: <20250717145216.85338-1-seanjc@google.com> (raw)
Please pull three TDX fixes for 6.16, two of which have potential to cause ABI
problems.
The following changes since commit 4578a747f3c7950be3feb93c2db32eb597a3e55b:
KVM: x86: avoid underflow when scaling TSC frequency (2025-07-09 13:52:50 -0400)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-fixes-6.16-rc7
for you to fetch changes up to b8be70ec2b47ca62ccb54dc3c2ab9a9c93653e00:
KVM: VMX: Ensure unused kvm_tdx_capabilities fields are zeroed out (2025-07-15 14:04:39 -0700)
----------------------------------------------------------------
KVM TDX fixes for 6.16
- Fix a formatting goof in the TDX documentation.
- Reject KVM_SET_TSC_KHZ for guests with a protected TSC (currently only TDX).
- Ensure struct kvm_tdx_capabilities fields that are not explicitly set by KVM
are zeroed.
----------------------------------------------------------------
Binbin Wu (1):
Documentation: KVM: Fix unexpected unindent warning
Kai Huang (1):
KVM: x86: Reject KVM_SET_TSC_KHZ vCPU ioctl for TSC protected guest
Sean Christopherson (1):
KVM: VMX: Ensure unused kvm_tdx_capabilities fields are zeroed out
Documentation/virt/kvm/api.rst | 11 +++++++++--
arch/x86/kvm/vmx/tdx.c | 7 ++++---
arch/x86/kvm/x86.c | 4 ++++
3 files changed, 17 insertions(+), 5 deletions(-)
next reply other threads:[~2025-07-17 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 14:52 Sean Christopherson [this message]
2025-07-17 15:09 ` Paolo Bonzini
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=20250717145216.85338-1-seanjc@google.com \
--to=seanjc@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®