mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Robert Love <rml@novell.com>
Subject: Re: How is user space notified of CPU speed changes?
Date: Fri, 22 Oct 2004 12:57:50 -0600	[thread overview]
Message-ID: <20041022185750.GT26297@schnapps.adilger.int> (raw)
In-Reply-To: <1098468316.5580.18.camel@krustophenia.net>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Oct 22, 2004  14:05 -0400, Lee Revell wrote:
> On Fri, 2004-10-22 at 07:23, Alan Cox wrote:
> > No it did not. It has never been a safe assumption. Even my old PC110
> > does APM non-linux assisted shifts between 8 16 and 33Mhz. In addition
> > there are boxes with dual CPU's and different multipliers - dual 
> > 300/450's were not uncommon.
> > 
> > And thats before we even mention such things at hyped-threading.
> 
> Seems like you are implying that any userspace app that needs to know
> the CPU speed is broken.  Is this correct?

Sadly, if I boot my laptop on battery and then plug it in, all of my
MP3s run twice (or whatever) as fast (XMMS on 2.4), making them sound like
the Chipmunks on crack.  I have to reboot my system while plugged in
to listen to music.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/             http://members.shaw.ca/golinux/


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-10-22 18:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 23:01 Lee Revell
2004-10-22 11:23 ` Alan Cox
2004-10-22 14:12   ` Con Kolivas
2004-10-22 18:05   ` Lee Revell
2004-10-22 18:57     ` Andreas Dilger [this message]
2004-10-22 19:40     ` Chris Friesen
2004-10-22 19:46       ` Lee Revell
2004-10-22 20:28       ` Alan Cox
2004-10-22 21:46         ` Chris Friesen
2004-10-22 23:25       ` Lee Revell
2004-10-25 15:28         ` Chris Friesen
2004-10-23  5:10   ` Lee Revell
2004-10-23 10:53     ` Matthew Garrett
2004-10-23 21:19     ` Alan Cox
2004-10-23 22:42       ` Lee Revell
2004-10-23 23:17         ` Jon Masters
2004-10-24  1:40           ` Lee Revell
2004-10-24 14:02         ` Alan Cox
2004-10-26  2:38           ` Lee Revell
2004-10-26  4:05           ` Lee Revell
2004-10-23 23:35       ` Jon Masters
2004-10-23 23:36         ` Jon Masters
2004-10-24 14:04         ` Alan Cox
2004-10-25  5:53         ` Joel Becker
2004-10-24 20:02     ` Robert Love
     [not found] <1098399709.4131.23.camel@krustophenia.net.suse.lists.linux.kernel>
     [not found] ` <1098444170.19459.7.camel@localhost.localdomain.suse.lists.linux.kernel>
     [not found]   ` <1098508238.13176.17.camel@krustophenia.net.suse.lists.linux.kernel>
     [not found]     ` <1098566366.24804.8.camel@localhost.localdomain.suse.lists.linux.kernel>
2004-10-23 23:54       ` Andi Kleen

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=20041022185750.GT26297@schnapps.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=rml@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®