On Wed, May 16, 2018 at 10:39:31AM +0200, Jiri Denemark wrote:
The new API computes the most feature-rich CPU which is compatible
with
all given CPUs and can be provided by the specified hypervisor. It is a
more useful version of vitConnectBaselineCPU, which doesn't consider any
hypervisor capabilities when computing the best CPU.
Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com>
---
include/libvirt/libvirt-host.h | 8 ++++
src/driver-hypervisor.h | 10 +++++
src/libvirt-host.c | 81 ++++++++++++++++++++++++++++++++++
src/libvirt_public.syms | 1 +
4 files changed, 100 insertions(+)
diff --git a/src/libvirt-host.c b/src/libvirt-host.c
index 17cf183499..cdbbe35e5a 100644
--- a/src/libvirt-host.c
+++ b/src/libvirt-host.c
@@ -1127,6 +1127,9 @@ virConnectGetCPUModelNames(virConnectPtr conn, const char *arch,
char ***models,
* Computes the most feature-rich CPU which is compatible with all given
* host CPUs.
*
+ * See vitConnectBaselineHypervisorCPU() to get a CPU which can be provided
The same rypo.
+ * by a specific hypervisor.
+ *
* If @flags includes VIR_CONNECT_BASELINE_CPU_EXPAND_FEATURES then libvirt
* will explicitly list all CPU features that are part of the host CPU,
* without this flag features that are part of the CPU model will not be
Reviewed-by: Ján Tomko <jtomko(a)redhat.com>
Jano