From: Pavel Machek <pavel@suse.cz>
To: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: rdtsc to mili secs?
Date: Tue, 14 Nov 2000 22:22:40 +0100 [thread overview]
Message-ID: <20001114222240.A1537@bug.ucw.cz> (raw)
In-Reply-To: <3A078C65.B3C146EC@mira.net> <E13t7ht-0007Kv-00@the-village.bc.nu> <20001110154254.A33@bug.ucw.cz> <8uhps8$1tm$1@cesium.transmeta.com>
In-Reply-To: <8uhps8$1tm$1@cesium.transmeta.com>; from H. Peter Anvin on Fri, Nov 10, 2000 at 01:38:16PM -0800
Hi!
> > > 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.
Don't think so. My toshiba is PIIX-based, AFAIC:
root@bug:~# cat /proc/pci
Bus 0, device 5, function 0:
Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 2).
Bus 0, device 5, function 1:
IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 1).
Master Capable. Latency=64.
I/O at 0x1000 [0x100f].
Bus 0, device 5, function 2:
USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 1).
IRQ 11.
Master Capable. Latency=64.
I/O at 0xffe0 [0xffff].
Bus 0, device 5, function 3:
Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 2).
Still, it is willing to run with RDTSC at 300MHz, 150MHz, and
40MHz. (The last one in _extreme_ cases when CPU fan fails -- running
at 40MHz is better than cooking cpu).
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
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/
next prev parent reply other threads:[~2000-11-15 21:34 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
2000-11-10 23:00 ` H. Peter Anvin
2000-11-14 21:22 ` Pavel Machek [this message]
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=20001114222240.A1537@bug.ucw.cz \
--to=pavel@suse.cz \
--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