linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
	Ashok Raj <ashok.raj@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: remove cpu hotplug bustification in cpufreq.
Date: Mon, 24 Jul 2006 17:59:23 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0607241752290.29649@g5.osdl.org> (raw)
In-Reply-To: <200607242023_MC3-1-C5FE-CADB@compuserve.com>



On Mon, 24 Jul 2006, Chuck Ebbert wrote:
> 
> I thought just the 'ondemand' governor was a problem?

The ondemand governor seems to be singled out not because it has unique 
problems, but because it seems to be used by Fedora Core for some strange 
reason.

I would judge that any bugs in cpufreq_ondemand.c are likely equally 
evident in cpufreq_conservative.c, for example. I think the two have the 
same background, and seem to have the same broken locking.

> That thing has been broken since day 1 AFAICT.  There are lots of
> reports of problems with it on the list.

See above. I seriously doubt this is ondemand-specific. The whole cpufreq 
locking seems to be very screwed up.

The current -git tree will complain about some of the more obvious 
problems. If you see a "Lukewarm IQ" message, it's a sign of somebody 
re-taking a cpu lock that is already held.

			Linus

  reply	other threads:[~2006-07-25  1:09 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25  0:21 remove cpu hotplug bustification in cpufreq Chuck Ebbert
2006-07-25  0:59 ` Linus Torvalds [this message]
2006-07-25 15:06   ` Erik Mouw
2006-07-25 18:54   ` Ingo Molnar
2006-07-25 19:30     ` Arjan van de Ven
2006-07-25 20:57       ` Linus Torvalds
2006-07-26 13:40         ` [patch] Reorganize the cpufreq cpu hotplug locking to not be totally bizare Arjan van de Ven
2006-07-26 15:51           ` Dave Jones
2006-07-26 17:09             ` Linus Torvalds
2006-07-26 19:42               ` Arjan van de Ven
2006-07-26 20:22                 ` Linus Torvalds
2006-07-26 20:58                   ` Srivatsa Vaddagiri
2006-07-26 21:29                     ` Linus Torvalds
2006-07-26 21:38                       ` Arjan van de Ven
2006-07-27  1:40                       ` Ingo Molnar
2006-07-27 17:38                         ` Ashok Raj
2006-07-29 13:45                           ` Ingo Molnar
2006-07-26 21:15                   ` Ashok Raj
2006-07-27 19:29                     ` Langsdorf, Mark
2006-07-28 13:50                       ` Andi Kleen
2006-07-28 17:09                         ` Langsdorf, Mark
2006-07-26 20:42                 ` Srivatsa Vaddagiri
2006-07-26 21:03                   ` Arjan van de Ven
2006-07-26 21:21                     ` Srivatsa Vaddagiri
2006-07-26 21:33                     ` Rafael J. Wysocki
2006-07-26 21:33                     ` Andrew Morton
2006-07-26 22:35                       ` Sanjoy Mahajan
2006-07-26 22:44                         ` Arjan van de Ven
2006-07-25 20:46     ` remove cpu hotplug bustification in cpufreq Dave Jones
2006-07-25 20:59       ` Linus Torvalds
2006-07-26 17:12       ` Russell King
2006-07-26 17:53         ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2006-07-22 19:40 Dave Jones
2006-07-23  0:10 ` Linus Torvalds
2006-07-23  1:06   ` Andrew Morton
2006-07-23  1:15     ` Linus Torvalds
2006-07-23  4:09       ` Arjan van de Ven
2006-07-23 17:20         ` Linus Torvalds
2006-07-23 18:12           ` Linus Torvalds
2006-07-23 18:34             ` Patrick McFarland
2006-07-24 10:52             ` Arjan van de Ven
2006-07-23  5:34       ` Andrew Morton
2006-07-23  8:29         ` Arjan van de Ven
2006-07-23 16:24         ` Ingo Molnar

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=Pine.LNX.4.64.0607241752290.29649@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=arjan@linux.intel.com \
    --cc=ashok.raj@intel.com \
    --cc=davej@redhat.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;
as well as URLs for NNTP newsgroup(s).