Re: [Xen-devel] [patch 14/33] xen: xen time implementation

2007-06-06 Thread Andi Kleen
On Wednesday 06 June 2007 12:05:22 Jeremy Fitzhardinge wrote: Jan Beulich wrote: Xen itself knows to deal with this (by using an error correction factor to slow down the local [TSC-based] clock), but for the kernel such a situation may be fatal: If clocksource-cycle_last was most recently

Re: [Xen-devel] [patch 14/33] xen: xen time implementation

2007-06-06 Thread Keir Fraser
On 6/6/07 12:00, Jan Beulich [EMAIL PROTECTED] wrote: If the error across CPUS is +/- just a few microseconds at worst then having the clocksource clamp to no less than the last timestamp returned seems a reasonable fix. Time won't 'stop' for longer than the cross-CPU error, and that

Re: [Xen-devel] [patch 14/33] xen: xen time implementation

2007-06-06 Thread Jan Beulich
Andi Kleen [EMAIL PROTECTED] 06.06.07 14:18 Yes, this could be an issue. Is there any way to get an interrupt or MCE when thermal throttling occurs? Yes you can get an thermal interrupt from the local APIC. See the Linux kernel source. Of course there would be still a race window. On the

Re: [Xen-devel] [patch 14/33] xen: xen time implementation

2007-06-06 Thread Andi Kleen
On Wednesday 06 June 2007 14:46:59 Jan Beulich wrote: Andi Kleen [EMAIL PROTECTED] 06.06.07 14:18 Yes, this could be an issue. Is there any way to get an interrupt or MCE when thermal throttling occurs? Yes you can get an thermal interrupt from the local APIC. See the Linux kernel