From: Clark Williams <williams@redhat.com>
To: "Mao Yilu" <ylmao@mail.ustc.edu.cn>
Cc: "'Henrique de Moraes Holschuh'" <hmh@hmh.eng.br>,
<linux-kernel@vger.kernel.org>
Subject: Re: TSC unstable on Intel Pentium M processor 750
Date: Thu, 30 Apr 2009 09:32:44 -0500 [thread overview]
Message-ID: <20090430093244.74fcb1af@torg> (raw)
In-Reply-To: <441077283.08393@ustc.edu.cn>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=US-ASCII, Size: 1400 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 30 Apr 2009 15:40:02 +0800
"Mao Yilu" <ylmao@mail.ustc.edu.cn> wrote:
> > -----Original Message-----
> > From: linux-kernel-owner@vger.kernel.org
> > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Henrique de Moraes
> > Holschuh
> > Sent: Thursday, April 30, 2009 11:12 AM
> > To: Mao Yilu
> > Cc: 'Robert Hancock'; linux-kernel@vger.kernel.org
> > Subject: Re: TSC unstable on Intel Pentium M processor 750
> >
> > On Thu, 30 Apr 2009, Mao Yilu wrote:
> > > But I still don't know why the TSC is not correct in the C1 state (hlt
> > > instruction). Is there anything more to influence the TSC? What happened
> > > when the CPU is not running under hlt instruction?
> >
> > SMIs? Laptops love that crap...
>
> What is SMIs?
>
>
System Management Interrupt. Usually handled by BIOS code and
completely invisible to Linux.
Laptops and big servers (rackmount/blades) typically have tons of SMIs
going off to do thermal management, statisics and remote management.
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
iEYEARECAAYFAkn5tpkACgkQHyuj/+TTEp1CjgCfZkG+/AU9CJrTSrk/+XVqPszS
4aoAoNgvDoLRMRUs1VSXqBRyg2HzPs6U
=drzY
-----END PGP SIGNATURE-----
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2009-04-30 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9E8AFFF282BE4091BA53C5D4F911F6F0@xiaomao>
2009-04-26 14:59 ` Mao Yilu
2009-04-29 23:50 ` Robert Hancock
[not found] ` <441049102.10204@ustc.edu.cn>
[not found] ` <654E14825BCE4C9B94E5986000DC9BCE@xiaomao>
2009-04-30 0:32 ` Mao Yilu
2009-04-30 3:11 ` Henrique de Moraes Holschuh
[not found] ` <441061189.03958@ustc.edu.cn>
[not found] ` <70DF5CB591F94B45BBC9BD2D41A047EF@xiaomao>
2009-04-30 7:40 ` Mao Yilu
2009-04-30 14:32 ` Clark Williams [this message]
2009-04-30 14:31 ` Henrique de Moraes Holschuh
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=20090430093244.74fcb1af@torg \
--to=williams@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=ylmao@mail.ustc.edu.cn \
/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
all inboxes | Powered by JetHome®