From: John Blackwood <john.blackwood@ccur.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org
Subject: [PATCH] cpufreq_conservative: initialize the cpu_dbs_info_s cpu field
Date: Tue, 23 Apr 2013 09:41:55 -0500 [thread overview]
Message-ID: <51769DB3.7030404@ccur.com> (raw)
In the cpufreq conservative module, the cpu field in the cpu_dbs_info_s
structure was not being initialized, and thus all cpus were scheduling
their do_dbs_timer() delayed work processing on cpu 0.
Signed-off-by: John Blackwood <john.blackwood@ccur.com>
Index: b/drivers/cpufreq/cpufreq_conservative.c
===================================================================
--- a/drivers/cpufreq/cpufreq_conservative.c
+++ b/drivers/cpufreq/cpufreq_conservative.c
@@ -506,6 +506,7 @@ static int cpufreq_governor_dbs(struct c
}
this_dbs_info->down_skip = 0;
this_dbs_info->requested_freq = policy->cur;
+ this_dbs_info->cpu = cpu;
mutex_init(&this_dbs_info->timer_mutex);
dbs_enable++;
next reply other threads:[~2013-04-23 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 14:41 John Blackwood [this message]
2013-04-23 15:19 ` [PATCH] cpufreq_conservative: initialize the cpu_dbs_info_s cpu field Viresh Kumar
2013-04-23 15:27 ` John Blackwood
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=51769DB3.7030404@ccur.com \
--to=john.blackwood@ccur.com \
--cc=cpufreq@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 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.