all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Jonas Theisen <j.theisen@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH qemu-server 09/15] helpers: add helper to query the host's TSC frequency and scaling support
Date: Wed, 18 Nov 2026 16:40:40 +0100	[thread overview]
Message-ID: <20261118154207.424260-10-j.theisen@proxmox.com> (raw)
In-Reply-To: <20261118154207.424260-1-j.theisen@proxmox.com>

Guests whose time stamp counter (TSC) frequency must not change across
a live migration need to know the TSC frequency of the host they are
started on, and whether the hosts in a cluster can scale the TSC
frequency for guests.

Query both directly from KVM, as there is no other interface that
reliably exposes them: upstream Linux does not export the TSC frequency
to user space, and the TSC scaling CPU flag is shown in different
places of /proc/cpuinfo for Intel and AMD CPUs, regardless of whether
KVM uses it.

KVM_GET_TSC_KHZ is a vCPU ioctl, so a temporary VM with a single vCPU
is created. This is cheap, as no guest memory is set up, and the
result is cached, as it cannot change while the host is running.

Signed-off-by: Jonas Theisen <j.theisen@proxmox.com>
---
 src/PVE/QemuServer/Helpers.pm | 53 +++++++++++++++++++++++++++++++++++
 1 file changed, 53 insertions(+)

diff --git a/src/PVE/QemuServer/Helpers.pm b/src/PVE/QemuServer/Helpers.pm
index 3932eb12..098d71eb 100644
--- a/src/PVE/QemuServer/Helpers.pm
+++ b/src/PVE/QemuServer/Helpers.pm
@@ -3,6 +3,7 @@ package PVE::QemuServer::Helpers;
 use strict;
 use warnings;
 
+use Fcntl qw(O_RDWR);
 use File::stat;
 use IO::File;
 
@@ -359,6 +360,58 @@ sub get_host_phys_address_bits {
     return; # undef, cannot really do anything..
 }
 
+# KVM ioctl request numbers and capabilities, see include/uapi/linux/kvm.h in Linux
+my $KVM_CREATE_VM = 0xae01;
+my $KVM_CHECK_EXTENSION = 0xae03;
+my $KVM_CREATE_VCPU = 0xae41;
+my $KVM_GET_TSC_KHZ = 0xaea3;
+my $KVM_CAP_TSC_CONTROL = 60;
+my $KVM_CAP_GET_TSC_KHZ = 61;
+
+my $_host_tsc_info;
+
+=head3 get_host_tsc_info
+
+    my $tsc_info = get_host_tsc_info();
+    my ($khz, $scaling) = $tsc_info->@{qw(khz scaling)};
+
+Returns a hash reference with information about the time stamp counter (TSC) of this host, as
+KVM reports it. C<khz> is the TSC frequency in kHz that KVM uses for new vCPUs, or undefined if
+KVM cannot report it. C<scaling> is true if KVM can run vCPUs with a different TSC frequency.
+
+The values are cached, as they cannot change while the host is running.
+
+Dies if C</dev/kvm> is not available.
+
+=cut
+
+sub get_host_tsc_info {
+    return $_host_tsc_info if defined($_host_tsc_info);
+
+    sysopen(my $kvm_fh, '/dev/kvm', O_RDWR) or die "unable to open /dev/kvm - $!\n";
+
+    my $check_extension = sub {
+        my ($cap) = @_;
+        return int(ioctl($kvm_fh, $KVM_CHECK_EXTENSION, $cap) // 0);
+    };
+
+    my $info = { scaling => $check_extension->($KVM_CAP_TSC_CONTROL) ? 1 : 0 };
+
+    # KVM_GET_TSC_KHZ is a vCPU ioctl, so it needs a temporary VM with a single vCPU
+    if ($check_extension->($KVM_CAP_GET_TSC_KHZ)) {
+        my $vm_fd = ioctl($kvm_fh, $KVM_CREATE_VM, 0) // die "unable to create KVM VM - $!\n";
+        open(my $vm_fh, '+<&=', int($vm_fd)) or die "unable to open KVM VM fd - $!\n";
+
+        my $vcpu_fd = ioctl($vm_fh, $KVM_CREATE_VCPU, 0) // die "unable to create KVM vCPU - $!\n";
+        open(my $vcpu_fh, '+<&=', int($vcpu_fd)) or die "unable to open KVM vCPU fd - $!\n";
+
+        my $khz = ioctl($vcpu_fh, $KVM_GET_TSC_KHZ, 0) // die "unable to get TSC frequency - $!\n";
+        $info->{khz} = int($khz) if int($khz) > 0;
+    }
+
+    return $_host_tsc_info = $info;
+}
+
 =head3 get_host_cpu_info
 
     my $info = get_host_cpu_info();
-- 
2.47.3





  parent reply	other threads:[~2026-11-18 15:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 15:40 [PATCH manager/qemu-server 00/15] check the target node's CPU before live migrating a VM Jonas Theisen
2026-11-18 15:40 ` [PATCH qemu-server 01/15] test: migration: allow checking for warnings and errors in the log Jonas Theisen
2026-11-18 15:40 ` [PATCH qemu-server 02/15] migrate: block live migration of host CPU VMs between CPU vendors Jonas Theisen
2026-11-18 15:40 ` [PATCH qemu-server 03/15] fix #6535: migrate: warn about live migration " Jonas Theisen
2026-11-18 15:40 ` [PATCH qemu-server 04/15] cpu flags: factor out parsing the broadcast CPU flags of a node Jonas Theisen
2026-11-18 15:40 ` [PATCH qemu-server 05/15] fix #2924: migrate: block live migration of host CPU VMs to nodes lacking flags Jonas Theisen
2026-11-18 15:40 ` [PATCH qemu-server 06/15] migrate: warn about live migration of host CPU VMs between CPU models Jonas Theisen
2026-11-18 15:40 ` [PATCH qemu-server 07/15] migrate: factor out whether the running virtual CPU is kept Jonas Theisen
2026-11-18 15:40 ` [PATCH qemu-server 08/15] migrate: block migration if the target cannot run the kept virtual CPU Jonas Theisen
2026-11-18 15:40 ` Jonas Theisen [this message]
2026-11-18 15:40 ` [PATCH qemu-server 10/15] cpu config: add hv-reenlightenment flag and set TSC frequency for it Jonas Theisen
2026-11-18 15:40 ` [PATCH qemu-server 11/15] migrate: block migration to nodes with incompatible TSC for re-enlightenment Jonas Theisen
2026-11-18 15:40 ` [PATCH manager 12/15] pvestatd: broadcast host CPU information relevant for live migration Jonas Theisen
2026-11-18 15:40 ` [PATCH manager 13/15] ui: migrate: show why the CPU of the target node is incompatible Jonas Theisen
2026-11-18 15:40 ` [PATCH manager 14/15] fix #6535: ui: migrate: show CPU warnings for the target node Jonas Theisen
2026-11-18 15:40 ` [PATCH manager 15/15] api: nodes: migrateall: skip VMs whose CPU is incompatible with the target Jonas Theisen

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=20261118154207.424260-10-j.theisen@proxmox.com \
    --to=j.theisen@proxmox.com \
    --cc=pve-devel@lists.proxmox.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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal