LKML Archive on
help / color / mirror / Atom feed
From: "Chris Friesen" <>
To: Jan Engelhardt <>
Cc: dean gaudet <>, "H. Peter Anvin" <>,,
Subject: Re: [PATCH] All Transmeta CPUs have constant TSCs
Date: Mon, 08 Jan 2007 14:51:31 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Pine.LNX.4.61.0701082118370.23737@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
> On Jan 8 2007 00:02, dean gaudet wrote:

>>transmeta decided years before intel and amd that a constant rate tsc 
>>(unaffected by P-state) was the only sane choice.  on transmeta cpus the 
>>tsc increments at the maximum cpu frequency no matter what the P-state 
>>(and no matter what longrun is doing behind the kernel's back).

> Well it defeats the purpose of TSC. I mean, they could have kept the "TSC" and
> instead added a second TSC ticker, constant_tsc.

Given that the name is "time stamp counter" then it makes sense to me to 
have a constant frequency.

For performance monitoring it would be useful to have a "cpu cycle 
counter" that counts clock cycles, and varies (and possibly stops) with 
the cpu itself.


  reply	other threads:[~2007-01-08 20:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05  1:48 H. Peter Anvin
2007-01-05 14:25 ` Jan Engelhardt
2007-01-08  8:02   ` dean gaudet
2007-01-08 20:19     ` Jan Engelhardt
2007-01-08 20:51       ` Chris Friesen [this message]
2007-01-08 20:51       ` H. Peter Anvin
2007-01-08 23:13         ` dean gaudet
2007-01-08 23:54           ` H. Peter Anvin

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] All Transmeta CPUs have constant TSCs' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).