From: Venki Pallipadi <venkatesh.pallipadi@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Support always running TSC on Intel CPUs
Date: Mon, 17 Nov 2008 17:05:28 -0800 [thread overview]
Message-ID: <20081118010528.GA22044@linux-os.sc.intel.com> (raw)
In-Reply-To: <492211C5.7090302@zytor.com>
On Mon, Nov 17, 2008 at 04:52:21PM -0800, H. Peter Anvin wrote:
> Venki Pallipadi wrote:
> > On Mon, Nov 17, 2008 at 04:18:16PM -0800, H. Peter Anvin wrote:
> >> Pallipadi, Venkatesh wrote:
> >>> All C-states higher than C1.
> >>>
> >> Including C2? If so, the TSC is unusable since C2 can be invoked
> >> asynchronously by the chipset.
> >>
> >
> > No. Not on Intel CPUs atleast. On Intel CPUs, we enter C-states only on
> > hlt or mwait. C1 is always C1 or C1E, where TSC always runs.
> > C2, C3, ... implementation vary depending on processor and TSC may or may
> > not run. This 0x80000007 feature bit basically says TSC is going to run
> > during any C-state.
> >
>
> I was under the impression that C2 was invoked by the chipset on a
> thermal condition, at least on older (P3-era) processors. Is that no
> longer true? If what you say is above (HLT and MWAIT only), then *was*
> it ever true?
I should also add io port based C-state to HLT and MWAIT. But, that again is
OS initiated.
I don't know of C2 invocation in thermal condition. Thermal condition, all
CPUs that I know of (P3 and beyond), use either clock modulation or frequency
changes. And on some such CPUs, where TSC runs at constant freq during such
modulation/freq change, we set CONSTANT_TSC bit based on model number check.
So, on CPUs earlier than those, we cannot use TSC or we have to scale TSC
based on freq. This patch shouldn't have any impact for those CPUs.
Thanks,
Venki
next prev parent reply other threads:[~2008-11-18 1:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 0:11 [PATCH] x86: Support always running TSC on Intel CPUs Venki Pallipadi
2008-11-18 0:13 ` H. Peter Anvin
2008-11-18 0:16 ` Pallipadi, Venkatesh
2008-11-18 0:18 ` H. Peter Anvin
2008-11-18 0:49 ` Venki Pallipadi
2008-11-18 0:52 ` H. Peter Anvin
2008-11-18 1:05 ` Venki Pallipadi [this message]
2008-11-18 1:07 ` H. Peter Anvin
2008-11-18 3:26 ` Arjan van de Ven
2008-11-18 3:27 ` H. Peter Anvin
2008-11-18 8:09 ` Ingo Molnar
2008-11-18 14:55 ` Joe Korty
2008-11-18 16:05 ` Ingo Molnar
2008-11-18 16:47 ` Pallipadi, Venkatesh
2008-11-18 16:54 ` Joe Korty
2008-11-18 17:01 ` H. Peter Anvin
2008-11-18 16:48 ` Joe Korty
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=20081118010528.GA22044@linux-os.sc.intel.com \
--to=venkatesh.pallipadi@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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