From: Dave Jones <davej@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: speedfreq: epia + longhaul + speedfreq + copying large files = freeze
Date: Thu, 23 Dec 2004 18:33:17 -0500 [thread overview]
Message-ID: <20041223233317.GF32326@redhat.com> (raw)
In-Reply-To: <1103832303.16431.60.camel@localhost>
On Thu, Dec 23, 2004 at 12:05:03PM -0800, Jeremy Fitzhardinge wrote:
> Sebastian is reporting the problem with speedfreqd, which will use the
> same number of steps both ways (and, depending on the CPU load curve, at
> the same rate).
>
> Does rate-limiting the transitions help stability?
that's something worth trying maybe.
> > We're not doing voltage scaling in longhaul yet, but that shouldn't
> > matter, as we should be booting at max voltage (as we boot at max speed)
>
> Is voltage switching complex? It might be worth trying - its not
> something which normally improves stability, but maybe there's some
> regulator issue under load changes, or something...
With longhaul, its a little more complicated than it is with powernow,
as theres no bios table telling us which voltage should be used
for each frequency, and they vary depending on stepping & speed of the part.
The first version of the longhaul driver did actually do voltage scaling,
but the 'match the voltage to the speed' code was very crude, and
assumed that the voltage table was 1:1 with the frequency, which
worked for the most part, but was far from being 'the right thing'.
I'm not convinced that adding it back in would fix the stability problems.
If anything, it would add another variable.
Dave
next prev parent reply other threads:[~2004-12-23 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41C83AA7.6010204@gmx.net>
2004-12-22 19:02 ` speedfreq: epia + longhaul + speedfreq + copying large files = freeze Jeremy Fitzhardinge
2004-12-22 20:31 ` Dave Jones
2004-12-23 2:38 ` Jeremy Fitzhardinge
2004-12-23 18:24 ` Dave Jones
2004-12-23 20:05 ` Jeremy Fitzhardinge
2004-12-23 23:33 ` Dave Jones [this message]
2004-12-23 11:15 ` Sebastian
2004-12-23 13:17 Sebastian
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=20041223233317.GF32326@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@www.linux.org.uk \
--cc=jeremy@goop.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 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.