Loading
Commits on Source 14
-
Peter Krempa authoredRegenerate with libvirt commit v12.0.0-206-gdbdaf22b63 to pick up the constants for histogram statistics. Signed-off-by:Peter Krempa <pkrempa@redhat.com>
-
Peter Krempa authored
Expose the fields accessed via VIR_DOMAIN_STATS_BLOCK_SUFFIX_LATENCY_HISTOGRAM_ constants as DomainStatsBlockLatencyHistogram. Signed-off-by: -
Peter Krempa authored
Signed-off-by: -
Daniel P. Berrangé authoredWhen "//export someMethod" is used, the Go method with the listed name is exported in the global linker namespace. If multiple Go modules export "someMethod" they will clash at link time. To address this, all exported Go methods will gain a 'virGo' prefix to scope them to libvirt's typical C namespace. The matching C helpers will also gain 'virGo' for consistency, even if they are static. Signed-off-by:Daniel P. Berrangé <berrange@redhat.com>
-
Daniel P. Berrangé authored
When "//export someMethod" is used, the Go method with the listed name is exported in the global linker namespace. If multiple Go modules export "someMethod" they will clash at link time. To address this, all exported Go methods will gain a 'virGo' prefix to scope them to libvirt's typical C namespace. The matching C helpers will also gain 'virGo' for consistency, even if they are static. Signed-off-by: -
Daniel P. Berrangé authored
When "//export someMethod" is used, the Go method with the listed name is exported in the global linker namespace. If multiple Go modules export "someMethod" they will clash at link time. To address this, all exported Go methods will gain a 'virGo' prefix to scope them to libvirt's typical C namespace. The matching C helpers will also gain 'virGo' for consistency, even if they are static. Signed-off-by: -
Daniel P. Berrangé authored
When "//export someMethod" is used, the Go method with the listed name is exported in the global linker namespace. If multiple Go modules export "someMethod" they will clash at link time. To address this, all exported Go methods will gain a 'virGo' prefix to scope them to libvirt's typical C namespace. The matching C helpers will also gain 'virGo' for consistency, even if they are static. Signed-off-by: -
Daniel P. Berrangé authored
When "//export someMethod" is used, the Go method with the listed name is exported in the global linker namespace. If multiple Go modules export "someMethod" they will clash at link time. To address this, all exported Go methods will gain a 'virGo' prefix to scope them to libvirt's typical C namespace. The matching C helpers will also gain 'virGo' for consistency, even if they are static. Signed-off-by: -
Daniel P. Berrangé authored
When "//export someMethod" is used, the Go method with the listed name is exported in the global linker namespace. If multiple Go modules export "someMethod" they will clash at link time. To address this, all exported Go methods will gain a 'virGo' prefix to scope them to libvirt's typical C namespace. The matching C helpers will also gain 'virGo' for consistency, even if they are static. Signed-off-by: -
Daniel P. Berrangé authored
When "//export someMethod" is used, the Go method with the listed name is exported in the global linker namespace. If multiple Go modules export "someMethod" they will clash at link time. To address this, all exported Go methods will gain a 'virGo' prefix to scope them to libvirt's typical C namespace. The matching C helpers will also gain 'virGo' for consistency, even if they are static. Signed-off-by: -
Daniel P. Berrangé authored
When "//export someMethod" is used, the Go method with the listed name is exported in the global linker namespace. If multiple Go modules export "someMethod" they will clash at link time. To address this, all exported Go methods will gain a 'virGo' prefix to scope them to libvirt's typical C namespace. The matching C helpers will also gain 'virGo' for consistency, even if they are static. Signed-off-by: -
Daniel P. Berrangé authored
When "//export someMethod" is used, the Go method with the listed name is exported in the global linker namespace. If multiple Go modules export "someMethod" they will clash at link time. To address this, all exported Go methods will gain a 'virGo' prefix to scope them to libvirt's typical C namespace. The matching C helpers will also gain 'virGo' for consistency, even if they are static. Signed-off-by: -
Daniel P. Berrangé authored
When "//export someMethod" is used, the Go method with the listed name is exported in the global linker namespace. If multiple Go modules export "someMethod" they will clash at link time. To address this, all exported Go methods will gain a 'virGo' prefix to scope them to libvirt's typical C namespace. The matching C helpers will also gain 'virGo' for consistency, even if they are static. Signed-off-by: -
Daniel P. Berrangé authored
When "//export someMethod" is used, the Go method with the listed name is exported in the global linker namespace. If multiple Go modules export "someMethod" they will clash at link time. To address this, all exported Go methods will gain a 'virGo' prefix to scope them to libvirt's typical C namespace. The matching C helpers will also gain 'virGo' for consistency, even if they are static. Signed-off-by: