linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, egor@pasemi.com, paulus@samba.org,
	arnd@arndb.de, cpufreq@lists.linux.org.uk
Subject: Re: [PATCH v2] [2.6.22] pasemi: cpufreq driver
Date: Thu, 26 Apr 2007 12:26:00 +0200	[thread overview]
Message-ID: <1177583160.6814.37.camel@johannes.berg> (raw)
In-Reply-To: <20070426053700.GA23922@lixom.net>

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

On Thu, 2007-04-26 at 00:37 -0500, Olof Johansson wrote:
> 
> +       policy->cur = pas_freqs[cur_astate].frequency;
> +       policy->cpus = cpu_possible_map; 

That doesn't seem right.

Either, all your processors scale along each other in which case you
should use cpu_online_map here, or they scale each on their own in which
case you just set a single bit here.

The generic code works like this:
CPU 0 is brought online and cpufreq initialised for it
CPU 1 is brought online and cpufreq initialised for it. if cpus includes
more than a single bit, cpufreq is linked to the first other CPU in
policy->cpus and then cpufreq for CPU1 is deinitialised again.

We have the same bug on powermac but for some reason the patch to fix it
that I posted a long time ago (look for "powermac: fix G5-cpufreq for
cpu on/offline") wasn't applied yet. Look at it though, it includes a
comment on what needs to be done.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2007-04-26 10:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25 20:46 [PATCH] [2.6.22] pasemi: cpufreq driver Olof Johansson
2007-04-25 23:47 ` Arnd Bergmann
2007-04-25 23:57   ` Olof Johansson
2007-04-26  1:57     ` Olof Johansson
2007-04-26  6:56   ` cbe_cpufreq crashes my machine Olof Johansson
2007-04-26  8:39     ` Benjamin Herrenschmidt
2007-04-26 23:07     ` [PATCH] cell: cbe_cpufreq cleanup and crash fix Olof Johansson
2007-04-27  5:22       ` [Cbe-oss-dev] " Akinobu Mita
2007-04-27  5:32         ` Olof Johansson
2007-04-27  5:33       ` [PATCH v2] " Olof Johansson
2007-04-27  7:55         ` Christian Krafft
2007-04-26  5:37 ` [PATCH v2] [2.6.22] pasemi: cpufreq driver Olof Johansson
2007-04-26  8:55   ` Arnd Bergmann
2007-04-26 16:48     ` Olof Johansson
2007-04-26 17:11       ` Arnd Bergmann
2007-04-26 19:05         ` Segher Boessenkool
2007-04-26 20:38           ` Olof Johansson
2007-04-27  0:10             ` Segher Boessenkool
2007-04-26 20:26         ` Olof Johansson
2007-04-26 20:43           ` Arnd Bergmann
2007-04-26 10:26   ` Johannes Berg [this message]
2007-04-26 20:37     ` Olof Johansson
2007-04-27  9:40       ` Johannes Berg
2007-04-27 18:09         ` Olof Johansson
2007-04-27  5:46   ` [PATCH v3] " Olof Johansson
2007-04-29  2:50     ` Dominik Brodowski
2007-04-29  3:40       ` Stephen Rothwell
2007-04-29  4:39         ` Olof Johansson
2007-04-29  4:42       ` Olof Johansson

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=1177583160.6814.37.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=arnd@arndb.de \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=egor@pasemi.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    --cc=paulus@samba.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).