From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [patch 14/33] xen: xen time implementation Date: Wed, 06 Jun 2007 14:46:59 +0200 Message-ID: <4666C8E3.76E4.0078.0@novell.com> References: <200706061418.28967.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <200706061418.28967.ak@suse.de> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andi Kleen , Keir Fraser Cc: Jeremy Fitzhardinge , Xen-devel , Andrew Morton , lkml , Chris Wright , virtualization@lists.osdl.org, Ingo Molnar , Linus Torvalds , Thomas Gleixner List-Id: virtualization@lists.linuxfoundation.org >>> Andi Kleen 06.06.07 14:18 >>> > >>=20 >> 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 other hand some timing issues on throttling are probably=20 >the smallest of the users' problems when it really happens. Not if this results in your box hanging - I think throttling is exactly = intended to keep the box alive as long as possible (and I've seen throttling in = action, with the box happily recovering from the situation - after having seen it = a few times I checked and found the fan covered with dust). >Standard Linux just ignores it. Jan