From: Kai Huang <kai.huang@intel.com>
To: seanjc@google.com, pbonzini@redhat.com
Cc: kvm@vger.kernel.org, thomas.lendacky@amd.com, nikunj@amd.com,
bp@alien8.de, isaku.yamahata@intel.com, xiaoyao.li@intel.com,
rick.p.edgecombe@intel.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Improve KVM_SET_TSC_KHZ handling for CoCo VMs
Date: Wed, 9 Jul 2025 17:37:58 +1200 [thread overview]
Message-ID: <cover.1752038725.git.kai.huang@intel.com> (raw)
This series follows Sean's suggestions [1][2] to:
- Reject vCPU scope KVM_SET_TSC_KHZ ioctl for TSC protected vCPU
- Reject VM scope KVM_SET_TSC_KHZ ioctl when vCPUs have been created
.. in the discussion of SEV-SNP Secure TSC support series.
This series has been sanity tested with TDX guests using today's Qemu:
- With this series Qemu can still run TDX guests successfully.
- With some hack to the Qemu, both VM and vCPU scope KVM_SET_TSC_KHZ
ioctls failed as expected.
Currently only TDX guests are TSC protected. The SEV-SNP Secure TSC
support will enable protected TSC too and can also benefit from this
series.
[1]: https://lore.kernel.org/kvm/aG0uUdY6QPnit6my@google.com/
[2]: https://lore.kernel.org/kvm/aG2k2BFBJHL-szZc@google.com/
Kai Huang (2):
KVM: x86: Reject KVM_SET_TSC_KHZ vCPU ioctl for TSC protected guest
KVM: x86: Reject KVM_SET_TSC_KHZ VM ioctl when vCPU has been created
arch/x86/kvm/x86.c | 8 ++++++++
1 file changed, 8 insertions(+)
base-commit: 6c7ecd725e503bf2ca69ff52c6cc48bb650b1f11
--
2.50.0
next reply other threads:[~2025-07-09 5:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 5:37 Kai Huang [this message]
2025-07-09 5:37 ` [PATCH 1/2] KVM: x86: Reject KVM_SET_TSC_KHZ vCPU ioctl for TSC protected guest Kai Huang
2025-07-09 6:40 ` Xiaoyao Li
2025-07-09 8:39 ` Nikunj A. Dadhania
2025-07-10 22:52 ` Huang, Kai
2025-07-11 6:22 ` Nikunj A Dadhania
2025-07-13 7:27 ` Huang, Kai
2025-07-09 5:38 ` [PATCH 2/2] KVM: x86: Reject KVM_SET_TSC_KHZ VM ioctl when vCPU has been created Kai Huang
2025-07-09 6:40 ` Xiaoyao Li
2025-07-09 8:34 ` Chao Gao
2025-07-09 13:55 ` Sean Christopherson
2025-07-10 22:53 ` Huang, Kai
2025-07-11 0:24 ` Huang, Kai
2025-07-11 2:17 ` Chao Gao
2025-07-11 2:46 ` Huang, Kai
2025-07-09 8:51 ` Nikunj A. Dadhania
2025-07-10 22:54 ` Huang, Kai
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=cover.1752038725.git.kai.huang@intel.com \
--to=kai.huang@intel.com \
--cc=bp@alien8.de \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=thomas.lendacky@amd.com \
--cc=xiaoyao.li@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
all inboxes | Powered by JetHome®