From: Bruno Ducrot <poup@poupinou.org>
To: dean gaudet <dean-list-linux-kernel@arctic.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: efficeon and longrun
Date: Tue, 30 Nov 2004 11:49:47 +0100 [thread overview]
Message-ID: <20041130104947.GA5744@poupinou.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0411291835500.18845@twinlark.arctic.org>
Hi,
On Mon, Nov 29, 2004 at 07:45:55PM -0800, dean gaudet wrote:
> On Tue, 30 Nov 2004, H. Peter Anvin wrote:
>
> > longrun-0.9 is hideously out of date, and was never debugged to begin
> > with. Given that these days longrun is handled via cpufreq, there
> > doesn't seem to be much reason for the standalone longrun program.
>
> the tool still has a place... for folks not using cpufreq/2.6 especially.
There is still a cpufreq/2.4 that I try sometimes to maintain and
support longrun.
> but also the longrun cpufreq driver is lacking support for
> scaling_available_frequencies, and doesn't display the voltages anywhere.
> in most cases the ACPI P-states driver works fine instead though.
That may be added if you justifies that enough. Apparently, you want a
fixed frequency cpufreq driver for longrun?
> i prefer the tool -- but then my requirements are pretty specific (i don't
> want cpufreq doing anything i'm not expecting while doing perf/debugging
> work).
cpufreq can help you IMHO. All the stuff you want can be done probably via
cpufreq. Debugging support, governors for your perf work if this is
done in kernel space, notifier interface, and last but not the
least, a more generic infrastructure so that you can change
processors or architectures at will.
Please ask what you need exactly but at the cpufreq mailing list.
Cheers,
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
prev parent reply other threads:[~2004-11-30 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 23:59 efficeon and longrun Ralph Metzler
2004-11-29 1:11 ` dean gaudet
2004-11-30 0:01 ` H. Peter Anvin
2004-11-30 3:45 ` dean gaudet
2004-11-30 10:49 ` Bruno Ducrot [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=20041130104947.GA5744@poupinou.org \
--to=poup@poupinou.org \
--cc=dean-list-linux-kernel@arctic.org \
--cc=hpa@zytor.com \
--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