All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 10055] conservative governor doesn't increase frequency, just decrease. powernow-k7
Date: Wed, 20 Feb 2008 16:44:36 -0800 (PST)	[thread overview]
Message-ID: <20080221004436.55103108010@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-10055-3570@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=10055


davej@codemonkey.org.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |trenn@suse.de




------- Comment #2 from davej@codemonkey.org.uk  2008-02-20 16:44 -------
Most obvious candidate for a problematic diff would be this patch I guess..

commit 1c2562459faedc35927546cfa5273ec6c2884cce
Author: Thomas Renninger <trenn@suse.de>
Date:   Tue Oct 2 13:28:12 2007 -0700

    [CPUFREQ] allow ondemand and conservative cpufreq governors to be used as
default

    Depending on the transition latency of the HW for cpufreq switches, the
    ondemand or conservative governor cannot be used with certain cpufreq
    drivers.  Still the ondemand should be the default governor on a wide range
    of systems.  This patch allows this and lets the governor fallback to the
    performance governor at cpufreq driver load time, if the driver does not
    support fast enough frequency switching.

    Main benefit is that on e.g.  installation or other systems without
    userspace support a working dynamic cpufreq support can be achieved on most
    systems by simply loading the cpufreq driver.  This is especially essential
    for recent x86(_64) laptop hardware which may rely on working dynamic
    cpufreq OS support.



Looking through it though, I'm not entirely clear how it could be at fault.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2008-02-21  0:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 19:40 [Bug 10055] New: conservative governor doesn't increase frequency, just decrease. powernow-k7 bugme-daemon
2008-02-20 23:52 ` [Bug 10055] " bugme-daemon
2008-02-21  0:44 ` bugme-daemon [this message]
2008-02-21  8:55 ` bugme-daemon
2008-02-24 23:01 ` bugme-daemon
2008-03-13 15:55 ` bugme-daemon
2008-06-01 23:57 ` bugme-daemon
2008-06-02  0:19 ` bugme-daemon
2008-07-29  8:37 ` bugme-daemon
2008-07-29  9:04 ` bugme-daemon
2008-08-01 17:19 ` bugme-daemon

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=20080221004436.55103108010@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=cpufreq@www.linux.org.uk \
    /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.