From: Len Brown <lenb@kernel.org>
To: Corrado Zoccolo <czoccolo@gmail.com>
Cc: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Andreas Mohr <andi@lisas.de>, LKML <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: Dynamic configure max_cstate
Date: Tue, 28 Jul 2009 15:25:12 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0907281522290.16740@localhost.localdomain> (raw)
In-Reply-To: <4e5e476b0907280020x242d9ef7gfa05c3d7b66f941f@mail.gmail.com>
> Entering a deep C state can cause strange things to timers: some of
> them, especially tsc, become unreliable.
The Nehalem family CPU has a non-stop constant-frequency TSC.
The measurements that Yanmin quotes show that the TSC
is the lowest overhead timesource in the system.
thanks,
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-07-28 19:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 5:30 Dynamic configure max_cstate Zhang, Yanmin
2009-07-27 7:33 ` Andreas Mohr
2009-07-28 2:42 ` Zhang, Yanmin
2009-07-28 7:20 ` Corrado Zoccolo
2009-07-28 9:00 ` Zhang, Yanmin
2009-07-28 10:11 ` Andreas Mohr
2009-07-28 14:03 ` Andreas Mohr
2009-07-28 17:35 ` ok, now would this be useful? (Re: Dynamic configure max_cstate) Andreas Mohr
2009-07-29 8:20 ` Dynamic configure max_cstate Zhang, Yanmin
2009-07-31 3:43 ` Robert Hancock
2009-07-31 7:06 ` Zhang, Yanmin
2009-07-31 8:07 ` Andreas Mohr
2009-07-31 14:40 ` Andi Kleen
2009-07-31 14:56 ` Michael S. Zick
2009-07-31 17:37 ` Pallipadi, Venkatesh
2009-07-31 15:14 ` Len Brown
2009-07-30 6:28 ` Zhang, Yanmin
2009-07-28 19:25 ` Len Brown [this message]
2009-07-29 0:17 ` Len Brown
2009-07-29 8:00 ` Andreas Mohr
2009-07-28 19:47 ` Len Brown
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=alpine.LFD.2.00.0907281522290.16740@localhost.localdomain \
--to=lenb@kernel.org \
--cc=andi@lisas.de \
--cc=czoccolo@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yanmin_zhang@linux.intel.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