Re: [PATCH 1/6] domain: introduce constants for virVcpuInfo->cpu state values

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

 



On 11/12/20 3:17 PM, Matt Coleman wrote:
On Nov 12, 2020, at 8:46 AM, Michal Privoznik <mprivozn@xxxxxxxxxx> wrote:

On 11/12/20 12:51 PM, Matt Coleman wrote:
+/**
+ * VIR_VCPU_INFO_CPU_OFFLINE:
+ *
+ * The VCPU is offline.
+ */
+# define VIR_VCPU_INFO_CPU_OFFLINE -1
+
+/**
+ * VIR_VCPU_INFO_CPU_UNAVAILABLE:
+ *
+ * The hypervisor does not expose real CPU information for VCPUs.
+ */
+# define VIR_VCPU_INFO_CPU_UNAVAILABLE -2
+
  /* Flags for controlling virtual CPU hot-plugging.  */
  typedef enum {
      /* See virDomainModificationImpact for these flags.  */

How about making this an enum instead?

Sounds good. I had done it this way based on the Hyper-V CPU details
thread. I'll update it to use an enum.


No need resend, I can fix that locally, if you agree.

Michal




[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]

  Powered by Linux