Re: [PATCHv4 2/4] vcpupin: implement the code to address the new API in the qemu driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 05/20/2011 04:09 AM, Taku Izumi wrote:
> --- libvirt.orig/src/qemu/qemu_driver.c
> +++ libvirt/src/qemu/qemu_driver.c
> @@ -2859,17 +2859,24 @@ qemudDomainSetVcpus(virDomainPtr dom, un
> 
> 
>  static int
> -qemudDomainPinVcpu(virDomainPtr dom,
> -                   unsigned int vcpu,
> -                   unsigned char *cpumap,
> -                   int maplen) {
> +qemudDomainPinVcpuFlags(virDomainPtr dom,
> +                        unsigned int vcpu,
> +                        unsigned char *cpumap,
> +                        int maplen,
> +                        unsigned int flags) {
> +
>      struct qemud_driver *driver = dom->conn->privateData;
>      virDomainObjPtr vm;
> +    virDomainDefPtr persistentDef = NULL;
>      int maxcpu, hostcpus;
>      virNodeInfo nodeinfo;
>      int ret = -1;
> +    bool isActive;
>      qemuDomainObjPrivatePtr priv;
> 
> +    virCheckFlags(VIR_DOMAIN_VCPU_LIVE |
> +                  VIR_DOMAIN_VCPU_CONFIG, -1);

Is this even possible since you already checked it at the top level?


-- 
Adam Litke
IBM Linux Technology Center

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]