cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 4379] Default sampling rates for ondemand governor are too high on a amd64
Date: Sat, 17 Nov 2007 23:02:08 -0800 (PST)	[thread overview]
Message-ID: <20071118070208.F228310806C@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-4379-3570@http.bugzilla.kernel.org/>

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


protasnb@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |protasnb@gmail.com




------- Comment #5 from protasnb@gmail.com  2007-11-17 23:02 -------
Eric, what about commit df8b59be0976c56820453730078bef99a8d1dbda, "Avoid the
ondemand cpufreq governor to use a too high frequency for stats" - does it
resolve this problem?
Thanks.


-- 
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.

       reply	other threads:[~2007-11-18  7:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-4379-3570@http.bugzilla.kernel.org/>
2007-11-18  7:02 ` bugme-daemon [this message]
2007-11-19 13:17 ` [Bug 4379] Default sampling rates for ondemand governor are too high on a amd64 bugme-daemon
2008-05-14 13:39 ` bugme-daemon
2008-05-14 13:44 ` bugme-daemon
2008-05-14 13:54 ` bugme-daemon
2008-05-15 18:12 ` bugme-daemon
2007-02-11  9:10 bugme-daemon
  -- strict thread matches above, loose matches on Subject: below --
2006-02-05 10:46 bugme-daemon
2005-11-15 21:59 bugme-daemon
2005-11-16  7:50 ` Eric Piel

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=20071118070208.F228310806C@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox