All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rutger Nijlunsing <rutger.nijlunsing@nospam.com>
To: cpufreq@www.linux.org.uk, linux-kernel@vger.kernel.org,
	moqua@kurtenba.ch
Subject: Re: cpufreq and p4 prescott
Date: Sun, 16 May 2004 15:20:20 +0200	[thread overview]
Message-ID: <20040516132020.GA14608@nospam.com> (raw)
In-Reply-To: <20040515194124.GA8212@dominikbrodowski.de>

> > The only thing I could find in Intel's documentation is the max. time
> > of throttling is 3 microseconds (p.67; 5.2.1 of Prescott
> > datasheet). So this 3 microseconds should correspond to 5600 ticks or
> > so...
> 
> Can't find it in the datasheets right now, but did find an interesting
> comment in section 13.15.3 of 24547212.pdf which explains the strange
> behaviour we're seeing.

Hm, 13.16.3 in my version, but indeed: all logical processors should
be put asleep in the same way ;)

> 
> > I know this is not P4 specific, but motherboard specific, but do
> > you know of modules which use motherboard specific knowledge to scale
> > the processor?
> No.
> > If the BIOS can do it, so should we be able to do it.
> 
> Dynamic frequency scaling is (probably) way different from setting a
> frequency at boot (which is what the BIOS does). Timing issues, settling
> times, etc. are way too complicated, AFAICS. Even trying to do this might
> result in severe non-recoverable hardware failures.

Probably true for some motherboards, but Asus got a WinXP program
called 'AiBooster' which is a program to under/overclock from -50% to
+33% runtime (butt-ugly UI can be seen in
http://www.asuscom.de/pub/ASUS/mb/sock478/p4p800/AIBooster_u.pdf). Could
Wine be used (given the right permissions) to run or disect such a
utility to make underclocking reality under Linux?

*hopeful* Or has Asus released the specification of its motherboard?

-- 
Rutger Nijlunsing ---------------------------- rutger ed tux tmfweb nl
never attribute to a conspiracy which can be explained by incompetence
----------------------------------------------------------------------

  reply	other threads:[~2004-05-16 13:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 17:39 cpufreq and p4 prescott Dominik Brodowski
2004-05-13 17:39 ` Dominik Brodowski
2004-05-14 21:47 ` rutger
2004-05-15  6:44   ` Dominik Brodowski
2004-05-15  6:44     ` Dominik Brodowski
2004-05-15 10:52     ` rutger
2004-05-15 19:41       ` Dominik Brodowski
2004-05-15 19:41         ` Dominik Brodowski
2004-05-16 13:20         ` Rutger Nijlunsing [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-12 17:14 Dominik Brodowski
2004-05-13  9:19 ` clemens kurtenbach
2004-05-13 15:30   ` rutger
2004-05-13 12:06 ` Dominik Brodowski
2004-05-12 15:28 clemens kurtenbach

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=20040516132020.GA14608@nospam.com \
    --to=rutger.nijlunsing@nospam.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux-kernel@tux.tmfweb.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moqua@kurtenba.ch \
    /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.