From: Dave Jones <davej@redhat.com>
To: Dominik Brodowski <linux@brodo.de>
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 02:26:13 +0000 [thread overview]
Message-ID: <20031121022613.GA15356@redhat.com> (raw)
In-Reply-To: <20031120183335.GB4425@brodo.de>
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.
Dave
next prev parent reply other threads:[~2003-11-21 2:26 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 [this message]
2003-11-21 9:56 ` Dominik Brodowski
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=20031121022613.GA15356@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@www.linux.org.uk \
--cc=linux@brodo.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.