From: Dominik Brodowski <linux@brodo.de>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@www.linux.org.uk
Subject: Re: [PATCH 5/8] p4_clockmod: detect speed without relying on cpu_khz or user input
Date: Fri, 21 Nov 2003 10:56:30 +0100 [thread overview]
Message-ID: <20031121095630.GA4148@brodo.de> (raw)
In-Reply-To: <20031121022613.GA15356@redhat.com>
On Fri, Nov 21, 2003 at 02:26:13AM +0000, Dave Jones wrote:
> On Thu, Nov 20, 2003 at 07:33:35PM +0100, Dominik Brodowski wrote:
> > On Wed, Nov 19, 2003 at 07:09:46PM +0000, Dave Jones wrote:
> > >
> > > patch 4/8 introduced what seems to be the exact same code in the speedstep-lib.
> > > Perhaps it belongs in an fsb.o instead that they can both share ?
> > > I don't mind duplicating it twice in object code, but having two copies
> > > in the source seems a bit silly.
> >
> > Usually, I agree to this topic. However, I don't want to create just another
> > file for just this function, and it doesn't belong to speedstep-lib either
> > as a plain p4 isn't a valid processor for speedstep-lib. So I'd prefer to
> > have this source code duplication as an exception here.
>
> Your call. I'm just concerned with the maintainence effort as this
> routine grows.
>
> As a sidenote, this could be useful outside of cpufreq at some point too.
> Alan tried adding 'overclocking detection' using these registers a while
> back. It is very difficult to get correct however, so it never came to
> anything. If we took the "perfect is the enemy of 'good enough'" approach
> and just did these checks for cpus we knew we do it correctly on, this
> would become feasable to pull off for 2.7.
Well, for Intel P3s and P4s the MSRs are eithre documented or reverse-
engineered quite well, so it should be something good to do in 2.7.[*]
Dominik
[*] which will hopefully be soon!
prev parent reply other threads:[~2003-11-21 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 18:32 [PATCH 5/8] p4_clockmod: detect speed without relying on cpu_khz or user input Dominik Brodowski
2003-11-19 19:09 ` Dave Jones
2003-11-20 18:33 ` Dominik Brodowski
2003-11-21 2:26 ` Dave Jones
2003-11-21 9:56 ` Dominik Brodowski [this message]
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=20031121095630.GA4148@brodo.de \
--to=linux@brodo.de \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.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