From a5036ccfd634186c57202c7f49c4eb6703911220 Mon Sep 17 00:00:00 2001
From: Peter Krempa <pkrempa@redhat.com>
Date: Wed, 20 Mar 2013 11:43:41 +0100
Subject: python: Fix emulatorpin API bindings

The addition of emulator pinning APIs didn't think of doing the right
job with python APIs for them. The default generator produced unusable
code for this.

This patch switches to proper code as in the case of domain Vcpu pining.
This change can be classified as a python API-breaker but in the state
the code was before I doubt anyone was able to use it successfully.
---
 libvirt-override-api.xml | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

(limited to 'libvirt-override-api.xml')

diff --git a/libvirt-override-api.xml b/libvirt-override-api.xml
index 2bd0e6a..155ab36 100644
--- a/libvirt-override-api.xml
+++ b/libvirt-override-api.xml
@@ -249,6 +249,20 @@
       <arg name='domain' type='virDomainPtr' info='pointer to domain object, or NULL for Domain0'/>
       <arg name='flags'  type='int' info='an OR&apos;ed set of virDomainModificationImpact'/>
     </function>
+    <function name='virDomainGetEmulatorPinInfo' file='python'>
+      <info>Query the CPU affinity setting of the emulator process of domain</info>
+      <return type='char *' info='the array of cpumap'/>
+      <arg name='domain' type='virDomainPtr' info='pointer to domain object'/>
+      <arg name='flags'  type='int' info='an OR&apos;ed set of virDomainModificationImpact'/>
+    </function>
+    <function name='virDomainPinEmulator' file='python'>
+      <info>Dynamically change the real CPUs which can be allocated to the emulator process of a domain.
+            This function requires privileged access to the hypervisor.</info>
+      <return type='int' info='0 in case of success, -1 in case of failure.'/>
+      <arg name='domain' type='virDomainPtr' info='pointer to domain object, or NULL for Domain0'/>
+      <arg name='cpumap' type='unsigned char *' info='pointer to a bit map of real CPUs (in 8-bit bytes) (IN) Each bit set to 1 means that corresponding CPU is usable. Bytes are stored in little-endian order: CPU0-7, 8-15... In each byte, lowest CPU number is least significant bit.'/>
+      <arg name='flags' type='int' info='flags to specify'/>
+    </function>
     <function name='virDomainSetSchedulerParameters' file='python'>
       <info>Change the scheduler parameters</info>
       <return type='int' info='-1 in case of error, 0 in case of success.'/>
-- 
cgit