public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: rdtsc to mili secs?
Date: Fri, 10 Nov 2000 23:23:48 +0100 (MET)	[thread overview]
Message-ID: <200011102223.XAA04330@cave.bitwizard.nl> (raw)
In-Reply-To: <8uhps8$1tm$1@cesium.transmeta.com> from "H. Peter Anvin" at "Nov 10, 2000 01:38:16 pm"

H. Peter Anvin wrote:
> Followup to:  <20001110154254.A33@bug.ucw.cz>
> By author:    Pavel Machek <pavel@suse.cz>
> In newsgroup: linux.dev.kernel
> > > 
> > > Sensibly configured power saving/speed throttle systems do not change the
> > > frequency at all. The duty cycle is changed and this controls the cpu 
> > > performance but the tsc is constant
> > 
> > Do you have an example of notebook that does powersaving like that?
> > I have 2 examples of notebooks with changing TSC speed...
> > 
> 
> Intel PIIX-based systems will do duty-cycle throttling, for example.

What's this "duty cycle throtteling"? Some people seem to think this
refers to changing the duty cycle on the clock, and thereby saving
power. I think it doesn't save any power if you do it that way. You
are referring to the duty cycle on a "stpclk" signal, right?


			Roger. 

> However, there are definitely notebooks that will mess with the
> frequency.  At Transmeta, we went through some considerable pain to
> make sure RDTSC would count walltime even across Longrun transitions.


-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
*       Common sense is the collection of                                *
******  prejudices acquired by age eighteen.   -- Albert Einstein ********
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-10 22:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-05 23:09 rdtsc to mili secs? Sushil Agarwal
2000-11-06  0:10 ` Andrea Arcangeli
2000-11-06  0:28   ` Alan Cox
2000-11-06  0:34     ` Andrea Arcangeli
2000-11-06  0:46       ` Alan Cox
2000-11-06 17:17     ` Anton Blanchard
2000-11-06 17:27       ` Alan Cox
2000-11-07  5:00       ` Antony Suter
2000-11-07  6:10         ` H. Peter Anvin
2000-11-07 12:18         ` Alan Cox
2000-11-10 14:42           ` Pavel Machek
2000-11-10 21:38             ` H. Peter Anvin
2000-11-10 22:23               ` Rogier Wolff [this message]
2000-11-10 23:00                 ` H. Peter Anvin
2000-11-14 21:22               ` Pavel Machek
2000-11-15 21:05                 ` H. Peter Anvin
2000-11-16 10:57                   ` Vojtech Pavlik
2000-11-16 23:09                     ` H. Peter Anvin
2000-11-18 20:13                       ` Pavel Machek
2000-11-18 23:48                         ` H. Peter Anvin
2000-11-19  9:21                           ` Vojtech Pavlik
2000-11-18 20:12                     ` Pavel Machek
2000-11-18 22:13                       ` Vojtech Pavlik
2000-11-19 20:24                         ` Pavel Machek
2000-11-19 21:46                           ` Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
2000-11-06  8:15 ming_l

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=200011102223.XAA04330@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /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