Re: [RFC 2/7] change headers preparing for steal time

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

 



 On 08/30/2010 03:44 PM, Glauber Costa wrote:
@@ -40,5 +40,7 @@ struct pvclock_wall_clock {
  } __attribute__((__packed__));

  #define PVCLOCK_TSC_STABLE_BIT	(1<<   0)
+#define PVCLOCK_STEAL_BIT   (2<<   0)
+
  #endif /* __ASSEMBLY__ */
  #endif /* _ASM_X86_PVCLOCK_ABI_H */
We could extend pvclock to 64 bytes (unfortunately we didn't reserve
bits 0-5 like we did with others) and use an nsec field.
Yes we could, but what for?
We're in a jiffie resolution on the other side anyway.

"the other side" keeps changing (and is potentially not just Linux). We need to be prepared for the future.

We'll regret having an interface that matches Linux at a random in time but nothing else.



--
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux