From: Len Brown <lenb@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>, Rob <roblinux@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: TSC as clocksource
Date: Mon, 10 Jan 2011 12:43:29 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.02.1101101237420.25082@x980> (raw)
In-Reply-To: <alpine.LFD.2.00.1101101452290.12146@localhost6.localdomain6>
> > On Mon, 2011-01-10 at 09:54 +1100, Rob wrote:
> > > Want to use TSC as clocksource
> > > have a Intel Core2 Duo with constant_tsc flag
> > > TSC should be stable at C1 + C2, it is debatable whether C3 is stable
no debate, TSC on Core2 stops in C3.
> > > Using processor.max_cstate=2 to use only C1 + C2 changes nothing, still get
> > > Monitor-Mwait will be used to enter C-3 state
> > > there should be checks before this is forced
>
> We unconditinally set TSC unstable for anything > C1. The reason is
> that we had a lot of troubles with BIOSes which advertise C2, but in
> fact implement C3. Unfortunately we can't verify that.
Right.
There are some Core2 where what ACPI advertises as C2 the TSC works,
and some where it does something other than "hardware C2",
such as "hardware C3" and the TSC stops, so Linux is conservative here.
If you want a stable TSC on Core2 (and before)
then you need to use either idle=poll or processor.max_cstate=1.
Nehalem and newer (Core i7 etc) have an invarient TSC that works no matter
what C-states are present.
cheers,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2011-01-10 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 22:54 TSC as clocksource Rob
2011-01-10 13:44 ` Peter Zijlstra
2011-01-10 13:54 ` Thomas Gleixner
2011-01-10 17:43 ` Len Brown [this message]
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.02.1101101237420.25082@x980 \
--to=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=roblinux@gmail.com \
--cc=tglx@linutronix.de \
/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