From: Andi Kleen <ak@suse.de>
To: Keir Fraser <keir@xensource.com>
Cc: Jan Beulich <jbeulich@novell.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Xen-devel] [patch 14/33] xen: xen time implementation
Date: Wed, 6 Jun 2007 14:18:28 +0200 [thread overview]
Message-ID: <200706061418.28967.ak@suse.de> (raw)
In-Reply-To: <C28C5EAB.1024D%keir@xensource.com>
>
> 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
the smallest of the users' problems when it really happens.
Standard Linux just ignores it.
-Andi
next parent reply other threads:[~2007-06-06 12:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C28C5EAB.1024D%keir@xensource.com>
2007-06-06 12:18 ` Andi Kleen [this message]
2007-06-06 12:46 ` [patch 14/33] xen: xen time implementation Jan Beulich
2007-06-06 12:53 ` Andi Kleen
2007-06-06 12:54 ` [Xen-devel] " Keir Fraser
2007-06-06 12:54 ` Keir Fraser
2007-06-06 11:00 Jan Beulich
2007-06-06 11:52 ` [Xen-devel] " Keir Fraser
2007-06-06 11:52 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2007-06-06 9:30 Jan Beulich
2007-06-06 9:56 ` [Xen-devel] " Keir Fraser
2007-06-06 9:56 ` Keir Fraser
2007-05-22 14:09 [patch 00/33] xen: Xen paravirt_ops implementation Jeremy Fitzhardinge
2007-05-22 14:09 ` [patch 14/33] xen: xen time implementation Jeremy Fitzhardinge
2007-06-06 8:39 ` Jan Beulich
2007-06-06 8:54 ` [Xen-devel] " Keir Fraser
2007-06-06 8:54 ` Keir Fraser
2007-06-06 10:05 ` Jeremy Fitzhardinge
2007-06-06 10:26 ` Andi Kleen
2007-06-06 14:15 ` [Xen-devel] " Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200706061418.28967.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=keir@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).