From: Viresh Kumar <viresh.kumar@linaro.org>
To: Valdis.Kletnieks@vt.edu
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: next-20130206 cpufreq - WARN in sysfs_add_one
Date: Fri, 8 Feb 2013 08:15:17 +0530 [thread overview]
Message-ID: <CAKohpoks+XA0bb33D53ZRxJaHzNk66++tBOrVhzMEhaM=7sbWA@mail.gmail.com> (raw)
In-Reply-To: <3542.1360264736@turing-police.cc.vt.edu>
On 8 February 2013 00:48, <Valdis.Kletnieks@vt.edu> wrote:
> On Thu, 07 Feb 2013 13:11:52 +0530, Viresh Kumar said:
>
>> First of all i want to confirm something about your system. I am sure it is a
>> multi-policy system (or multi cluster system). i.e. there are more than one
>> clock line for different cpus ? And so multiple struct policy exist
>> simultaneously.
>
> Hmm.. it's a bog-standard Dell Latitude E6500 laptop, with a single
> Core2 Duo P8700 CPU (one die, 2 cores, no HT). It's apparently able
> to clock both cores at different speeds (one core running busy at 2540mhz
> and the other idling at 800mhz), if that's what you mean by multiple
> clock lines.
Perfect!! So, when the cpus can manage different freqs, we have multiple
struct policies for them per cpu.
> In any case, next-20130206 complained, and with this patch added I see
> nothing in dmesg and cpufreq is acting properly on both cores, so:
>
> Tested-By: Valdis Kletnieks <valdis.kletnieks@vt.edu>
Thanks.
> (btw - I had to hand-apply your patch, as it showed up white-space
> damaged. Three lines wrapped, and tabs converted to spaces).
I know that and feeling bad for you :(
I gave you this because of my mails issue :)
http://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/heads/for-valdis
prev parent reply other threads:[~2013-02-08 2:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 17:44 next-20130206 cpufreq - WARN in sysfs_add_one Valdis Kletnieks
2013-02-06 21:24 ` Rafael J. Wysocki
2013-02-07 0:55 ` Valdis.Kletnieks
2013-02-07 1:12 ` Rafael J. Wysocki
2013-02-07 2:03 ` Rafael J. Wysocki
2013-02-07 7:41 ` Viresh Kumar
2013-02-07 19:18 ` Valdis.Kletnieks
2013-02-08 2:45 ` Viresh Kumar [this message]
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='CAKohpoks+XA0bb33D53ZRxJaHzNk66++tBOrVhzMEhaM=7sbWA@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).