linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Sven Geggus <geg@iitb.fhg.de>, linux-kernel@vger.kernel.org
Subject: Re: Changing CPU Speed while running Linux
Date: Thu, 14 Jun 2001 13:12:20 +0000	[thread overview]
Message-ID: <20010614131220.A36@toy.ucw.cz> (raw)
In-Reply-To: <20010613143536.A1323@iitb.fhg.de> <3B2768E1.2B7E064C@redhat.com>
In-Reply-To: <3B2768E1.2B7E064C@redhat.com>; from arjanv@redhat.com on Wed, Jun 13, 2001 at 02:21:37PM +0100

Hi

> > on my Elan410 based System it is very easy to change the CPU clock speed by
> > means od two outb commands.
> > 
> > I was wondering, if it does some harm to the Kernel if the CPU is
> > reprogrammed using a different CPU clock speed, while the system is up and
> > running.
> 
> I have a module for the K6 PowerNow which allows you to do
> 
> echo 450 > /proc/sys/cpu/0/frequency
> 
> and does the right thing wrt udelay / bogomips etc..
> I can dig it out if you want.. sounds like this should be a more generic
> thing.

Can you dig that out? I'd like to take a look.

[Of course, problem is *not* solved: you still have short time when
kernel runs with wrong bogomips.]

-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  reply	other threads:[~2001-06-16 10:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 12:35 Changing CPU Speed while running Linux Sven Geggus
2001-06-13 13:21 ` Arjan van de Ven
2001-06-14 13:12   ` Pavel Machek [this message]
2001-06-16 10:46     ` arjan
2001-06-16 13:23     ` Alan Cox
2001-06-16 13:56       ` Ian Stirling
2001-06-13 13:41 ` Magnus Sandberg
2001-06-13 13:49   ` Dave Jones
2001-06-13 22:23 Dieter Nützel

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=20010614131220.A36@toy.ucw.cz \
    --to=pavel@suse.cz \
    --cc=arjanv@redhat.com \
    --cc=geg@iitb.fhg.de \
    --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;
as well as URLs for NNTP newsgroup(s).