All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: markh@compro.net
Cc: Arjan van de Ven <arjan@infradead.org>,
	"linux-os (Dick Johnson)" <linux-os@analogic.com>,
	Jan Engelhardt <jengelh@medozas.de>,
	"Kok, Auke" <auke-jan.h.kok@intel.com>,
	"solsTiCe d'Hiver" <solstice.dhiver@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: no cpu MHz in /proc/cpuinfo on 2.6.25.4-rt6
Date: Wed, 11 Jun 2008 15:39:24 -0600	[thread overview]
Message-ID: <4850460C.5030406@nortel.com> (raw)
In-Reply-To: <48503EB9.6000606@compro.net>

Mark Hounschell wrote:

> If they are not the same how do you know at what rate the tsc is counting.

You don't, at least not easily.  The timekeeping subsystem knows, but it 
might be unstable, or change with cpu frequency or cpu going idle, etc.

> But back to "how usable is rdtsc for time", is there a
> 
> clock_gettime(CLOCK_MONOTONIC, &time) equivalent that can be used in the kernel?

With current kernels it looks like ktime_get_ts() should give exactly 
the same results, since it's how that userspace function is implemented. 
  With a stable tsc it seems like it should give full accuracy.

Chris

  parent reply	other threads:[~2008-06-11 21:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 19:52 PROBLEM: no cpu MHz in /proc/cpuinfo on 2.6.25.4-rt6 solsTiCe d'Hiver
2008-06-10 20:13 ` Arjan van de Ven
2008-06-10 20:42   ` Kok, Auke
2008-06-11 12:42     ` Jan Engelhardt
2008-06-11 13:36       ` Arjan van de Ven
2008-06-11 13:52         ` Jan Engelhardt
2008-06-11 13:58           ` Arjan van de Ven
2008-06-11 14:14             ` linux-os (Dick Johnson)
2008-06-11 15:10               ` Peter Zijlstra
2008-06-11 15:36               ` Arjan van de Ven
2008-06-11 16:59                 ` Mark Hounschell
2008-06-11 17:44                   ` Arjan van de Ven
2008-06-11 17:54                     ` Mark Hounschell
2008-06-11 20:29                       ` Arjan van de Ven
2008-06-11 20:37                       ` Mark Hounschell
2008-06-11 20:55                         ` Arjan van de Ven
2008-06-11 20:59                           ` Mark Hounschell
2008-06-11 20:58                         ` Arjan van de Ven
2008-06-11 21:08                           ` Mark Hounschell
2008-06-11 21:28                             ` Arjan van de Ven
2008-06-11 21:39                             ` Chris Friesen [this message]
2008-06-11 23:08                       ` Andi Kleen
2008-06-11 16:08         ` Ray Lee
2008-06-11 16:32           ` Arjan van de Ven
2008-06-11 12:40 ` Jan Engelhardt
2008-06-11 14:15   ` solsTiCe d'Hiver
2008-06-11 14:36     ` Jan Engelhardt
2008-06-11 15:35       ` solsTiCe d'Hiver

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=4850460C.5030406@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=arjan@infradead.org \
    --cc=auke-jan.h.kok@intel.com \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=markh@compro.net \
    --cc=solstice.dhiver@gmail.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.