From: Michael Buesch <fsdeveloper@yahoo.de>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5 'what to expect' document.
Date: Mon, 14 Apr 2003 23:25:53 +0200 [thread overview]
Message-ID: <200304142325.47325.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <20030414211311.GA11160@suse.de>
On Monday 14 April 2003 23:13, Dave Jones wrote:
> On Mon, Apr 14, 2003 at 11:08:03PM +0200, Michael Buesch wrote:
> > Will it be implemented in future to taint the kernel if CPU is
> > overclocked?
>
> Theoretically possible on most CPUs, but it's not that simple.
> - Some CPUs don't encode the necessary bits to tell you their
> current multiplier/FSB
> - Some CPUs don't encode the necessary info to tell you the speed
> the CPU should be running at.
I know. That was exactly the reason for I asked. :)
--
Regards Michael Buesch.
http://www.8ung.at/tuxsoft
$ cat /dev/zero > /dev/null
/dev/null: That's *not* funny! :(
next prev parent reply other threads:[~2003-04-14 21:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 19:31 2.5 'what to expect' document Dave Jones
2003-04-14 21:08 ` Michael Buesch
2003-04-14 21:13 ` Dave Jones
2003-04-14 21:25 ` Michael Buesch [this message]
2003-04-14 21:48 ` Sam Ravnborg
2003-04-14 21:57 ` Robert Love
2003-04-15 5:13 ` Sam Ravnborg
2003-04-14 21:59 ` Valdis.Kletnieks
2003-04-14 22:07 ` Robert Love
2003-04-15 0:15 ` Wichert Akkerman
2003-04-15 5:15 ` Randy.Dunlap
2003-04-15 11:06 ` Dave Jones
2003-04-15 5:19 ` Nigel Cunningham
2003-04-15 11:07 ` Dave Jones
2003-04-15 21:24 ` Nigel Cunningham
2003-04-15 21:29 ` Randy.Dunlap
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=200304142325.47325.fsdeveloper@yahoo.de \
--to=fsdeveloper@yahoo.de \
--cc=davej@codemonkey.org.uk \
--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