29.09.2010 12:28, Avi Kivity wrote: > On 08/03/2010 12:35 AM, Arjan Koers wrote: >> I don't think that pvclock_clocksource_read is receiving >> completely random uninitialized data. The values in shadow >> are wrong, but could be interpreted as valid data >> (shadow.tsc_to_nsec_mul = b6dc43b6, shadow.tsc_shift = ffffffff, >> shadow.flags = 0 and shadow.version is always even). >> >> I've attached the printk patches for 2.6.34.1 and 2.6.35, in case >> anyone needs them... [Move a printk that's using the clock before it's ready] > Thanks, applied. Please post patches in a new thread so I get the > chance to see them. Avi, this is definitely a -stable material, for 2.6.32 (longterm stable) and 2.6.35. /mjt -- 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
