All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Venki Pallipadi <venkatesh.pallipadi@intel.com>
Cc: 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 16:13:50 -0800	[thread overview]
Message-ID: <492208BE.2000001@zytor.com> (raw)
In-Reply-To: <20081118001137.GA12350@linux-os.sc.intel.com>

Venki Pallipadi wrote:
> Add support for CPUID_0x80000007_Bit8 on Intel CPUs as well. This bit means
> that the TSC is invariant with C/P/T states and always runs at constant
> frequency.
> 
> With Intel CPUs, we have 3 classes
> * CPUs where TSC runs at constant rate and does not stop n C-states
> * CPUs where TSC runs at constant rate, but will stop in deep C-states
> * CPUs where TSC rate will vary based on P/T-states and TSC will stop in deep
>   C-states.
> 
> To cover these 3, one feature bit (CONSTANT_TSC) is not enough. So, add a
> second bit (NOSTOP_TSC). CONSTANT_TSC indicates that the TSC runs at
> constant frequency irrespective of P/T-states, and NOSTOP_TSC indicates
> that TSC does not stop in deep C-states.
> 

What is the definition of a "deep" C-state?  C2?  C3?  C4?

	-hpa

  reply	other threads:[~2008-11-18  0:14 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 [this message]
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
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=492208BE.2000001@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.