mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-22 21:55:25 +00:00
0ba3870406
When introducing VIR_DOMAIN_IOTHREAD_THREAD_POOL_MIN and VIR_DOMAIN_IOTHREAD_THREAD_POOL_MAX typed parameters, I've made a shortcut. Since at the monitor level these two are set in two separate calls and minimum has to be always smaller than maximum (or equal to it), it may happen that one of the values we want to set violates this restriction. So I've put a little note in the public API description warning users about this. However, the proper solution is to have a logic that checks the current values and based on that set either minimum or maximum value first. But until we get there, remove that note from the public API before it gets released. Related: https://gitlab.com/libvirt/libvirt/-/issues/339 Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> |
||
|---|---|---|
| .. | ||
| libvirt-admin.h | ||
| libvirt-common.h.in | ||
| libvirt-domain-checkpoint.h | ||
| libvirt-domain-snapshot.h | ||
| libvirt-domain.h | ||
| libvirt-event.h | ||
| libvirt-host.h | ||
| libvirt-interface.h | ||
| libvirt-lxc.h | ||
| libvirt-network.h | ||
| libvirt-nodedev.h | ||
| libvirt-nwfilter.h | ||
| libvirt-qemu.h | ||
| libvirt-secret.h | ||
| libvirt-storage.h | ||
| libvirt-stream.h | ||
| libvirt.h | ||
| meson.build | ||
| virterror.h | ||