ef809b76a6
- esxConnectListAllDomains: Don't propagate failure to lookup a single domain (RHEL-80606) - conf: parse interface/source/@dev for all interface types (with backend type='passt') (RHEL-82539) - libvirt-host: Clarify/fix description of the CPU frequency field (RHEL-86197) - virNodeGetInfo: Improve description of the case when fake data is reported (RHEL-86197) - manpages: virsh: Use disclaimer from 'virNodeGetInfo()' for 'virsh nodeinfo' (RHEL-86197) - esx: Accept empty "path" URI component same way as "/" (RHEL-86459) - qemu: Rename outgoingMigration parameter in various TPM functions (RHEL-86800) - qemu: Properly propagate migration state to TPM cleanup code (RHEL-86800) - qemuDomainBlockCopyCommon: Don't revoke access to file twice on failure (RHEL-7357) - qemuxmlconftest: Drop s390-default-cpu-...ccw-virtio-2.7 test cases (RHEL-72976) - tests: add capabilities for QEMU 10.0.0 on s390x (RHEL-72976) - qemu: Do NOT autoadd NUMA node for s390 (RHEL-72976) - qemu_command: Use qemuBuildVirtioDevProps() to build cmd line for virtio-mem and virtio-pmem (RHEL-72976) - qemuxmlconftest: Introduce memory-hotplug-virtio-mem-pci-s390x.xml (RHEL-72976) - qemu_caps: Introduce QEMU_CAPS_DEVICE_VIRTIO_MEM_CCW (RHEL-72976) - qemu: Validate virtio-mem-ccw (RHEL-72976) - qemu: Allow virtio-mem on CCW (RHEL-72976) - qemuxmlconftest: Introduce memory-hotplug-virtio-mem-ccw-s390x.xml (RHEL-72976) - qemu_domain_address: fix CCW virtio-mem hotplug (RHEL-72976) Resolves: RHEL-72976, RHEL-7357, RHEL-80606, RHEL-82539, RHEL-86197 Resolves: RHEL-86459, RHEL-86800
52 lines
2.2 KiB
Diff
52 lines
2.2 KiB
Diff
From a96d1c90832b639c81f6cd893a79610d4379594d Mon Sep 17 00:00:00 2001
|
|
Message-ID: <a96d1c90832b639c81f6cd893a79610d4379594d.1744876587.git.jdenemar@redhat.com>
|
|
From: Peter Krempa <pkrempa@redhat.com>
|
|
Date: Mon, 7 Apr 2025 13:35:37 +0200
|
|
Subject: [PATCH] libvirt-host: Clarify/fix description of the CPU frequency
|
|
field
|
|
|
|
The 'virNodeInfo' field for CPU frequency is named 'mhz'. The docs were
|
|
mentioning 'mHZ', which is neither the field name nor proper spelling of
|
|
the unit.
|
|
|
|
Reword the paragraph to mention "CPU frequency" instead and explicitly
|
|
name the field in virNodeInfo struct.
|
|
|
|
Signed-off-by: Peter Krempa <pkrempa@redhat.com>
|
|
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
|
|
(cherry picked from commit e54cc1500ccfb36cd5b67eb4d886c491fdda5b2b)
|
|
|
|
https://issues.redhat.com/browse/RHEL-86197
|
|
---
|
|
src/libvirt-host.c | 8 ++++----
|
|
1 file changed, 4 insertions(+), 4 deletions(-)
|
|
|
|
diff --git a/src/libvirt-host.c b/src/libvirt-host.c
|
|
index b3a6421a7f..318a664d24 100644
|
|
--- a/src/libvirt-host.c
|
|
+++ b/src/libvirt-host.c
|
|
@@ -410,9 +410,9 @@ virConnectGetMaxVcpus(virConnectPtr conn,
|
|
* Use of this API is strongly discouraged as the information provided
|
|
* is not guaranteed to be accurate on all hardware platforms.
|
|
*
|
|
- * The mHZ value merely reflects the speed that the first CPU in the
|
|
- * machine is currently running at. This speed may vary across CPUs
|
|
- * and changes continually as the host OS throttles.
|
|
+ * The CPU frequency value (field 'mhz' in virNodeInfo) merely reflects the
|
|
+ * speed that the first CPU in the machine is currently running at. This speed
|
|
+ * may vary across CPUs and changes continually as the host OS throttles.
|
|
*
|
|
* The nodes/sockets/cores/threads data is potentially inaccurate as
|
|
* it assumes a symmetric installation. If one NUMA node has more
|
|
@@ -420,7 +420,7 @@ virConnectGetMaxVcpus(virConnectPtr conn,
|
|
* wrong. It is also not able to report about CPU dies.
|
|
*
|
|
* Applications are recommended to use the virConnectGetCapabilities()
|
|
- * call instead, which provides all the information except CPU mHZ,
|
|
+ * call instead, which provides all the information except CPU frequency,
|
|
* in a more accurate representation.
|
|
*
|
|
* Returns 0 in case of success and -1 in case of failure.
|
|
--
|
|
2.49.0
|