From: arjan@fenrus.demon.nl
To: pavel@suse.cz (Pavel Machek)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Changing CPU Speed while running Linux
Date: Sat, 16 Jun 2001 11:46:08 +0100 (BST) [thread overview]
Message-ID: <m15BDai-000OrcC@amadeus.home.nl> (raw)
In-Reply-To: <20010614131220.A36@toy.ucw.cz>
In article <20010614131220.A36@toy.ucw.cz> you wrote:
>> 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.]
But the kernel controls that time ..... It's not perfect, and it might be
aleviated by going in small steps at a time.
Disabling interrupts isn't fun as the bogomips code kind of needs that ;)
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2001-06-16 10:47 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
2001-06-16 10:46 ` arjan [this message]
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=m15BDai-000OrcC@amadeus.home.nl \
--to=arjan@fenrus.demon.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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).