[libvirt] [PATCH v4 3/4] vcpupin: implement the remote protocol to address the new API
Hu Tao
hutao at cn.fujitsu.com
Fri Jun 10 08:25:44 UTC 2011
> Index: libvirt/src/remote/remote_driver.c
> ===================================================================
> --- libvirt.orig/src/remote/remote_driver.c
> +++ libvirt/src/remote/remote_driver.c
> @@ -6259,6 +6259,7 @@ static virDriver remote_driver = {
> .domainSetVcpusFlags = remoteDomainSetVcpusFlags, /* 0.8.5 */
> .domainGetVcpusFlags = remoteDomainGetVcpusFlags, /* 0.8.5 */
> .domainPinVcpu = remoteDomainPinVcpu, /* 0.3.0 */
> + .domainPinVcpuFlags = remoteDomainPinVcpuFlags, /* 0.9.3 */
gcc gives a warning here. the generated remoteDomainPinVcpuFlags is
defined as:
static int
remoteDomainPinVcpuFlags(virDomainPtr dom, int vcpu, const char *cpumap,
int cpumaplen, unsigned int flags)
but .domainPinVcpuFlags is of type:
typedef int
(*virDrvDomainPinVcpuFlags) (virDomainPtr domain,
unsigned int vcpu,
unsigned char *cpumap,
int maplen,
unsigned int flags);
--
Thanks,
Hu Tao
More information about the libvir-list
mailing list