From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Pierre Ossman <pierre-list@ossman.eu>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq, powernow-k8: Initialize per-cpu data-structures properly
Date: Mon, 17 Feb 2014 23:02:50 +0100 [thread overview]
Message-ID: <1851033.kRQPL2X90T@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpo=nYQpZFh5=2g=REDyf-LKaMqJvnZ=pSncawLFpr1K_+Q@mail.gmail.com>
On Monday, February 17, 2014 04:35:08 PM Viresh Kumar wrote:
> On 17 February 2014 16:18, Srivatsa S. Bhat
> <srivatsa.bhat@linux.vnet.ibm.com> wrote:
> > The powernow-k8 driver maintains a per-cpu data-structure called powernow_data
> > that is used to perform the frequency transitions. It initializes this data-
> > structure only for the policy->cpu. So, accesses to this data-structure by
> > other CPUs results in various problems because they would have been
> > uninitialized.
> >
> > Specifically, if a cpu (!= policy->cpu) invokes the drivers' ->get() function,
> > it returns 0 as the KHz value, since its per-cpu memory doesn't point to
> > anything valid. This causes problems during suspend/resume since
> > cpufreq_update_policy() tries to enforce this (0 KHz) as the current frequency
> > of the CPU, and this madness gets propagated to adjust_jiffies() as well.
> > Eventually, lots of things start breaking down, including the r8169 ethernet
> > card, in one particularly interesting case reported by Pierre Ossman.
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=70311
> >
> > Fix this by initializing the per-cpu data-structures of _all_ the CPUs
> > in the policy appropriately.
> >
> > Cc: stable@vger.kernel.org
> > Reported-by: Pierre Ossman <pierre@ossman.eu>
> > Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
> > ---
> >
> > drivers/cpufreq/powernow-k8.c | 10 +++++++---
> > 1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/cpufreq/powernow-k8.c b/drivers/cpufreq/powernow-k8.c
> > index e10b646..6684e03 100644
> > --- a/drivers/cpufreq/powernow-k8.c
> > +++ b/drivers/cpufreq/powernow-k8.c
> > @@ -1076,7 +1076,7 @@ static int powernowk8_cpu_init(struct cpufreq_policy *pol)
> > {
> > struct powernow_k8_data *data;
> > struct init_on_cpu init_on_cpu;
> > - int rc;
> > + int rc, cpu;
> >
> > smp_call_function_single(pol->cpu, check_supported_cpu, &rc, 1);
> > if (rc)
> > @@ -1140,7 +1140,9 @@ static int powernowk8_cpu_init(struct cpufreq_policy *pol)
> > pr_debug("cpu_init done, current fid 0x%x, vid 0x%x\n",
> > data->currfid, data->currvid);
> >
> > - per_cpu(powernow_data, pol->cpu) = data;
> > + /* Point all the CPUs in this policy to the same data */
> > + for_each_cpu(cpu, pol->cpus)
> > + per_cpu(powernow_data, cpu) = data;
> >
> > return 0;
> >
> > @@ -1155,6 +1157,7 @@ err_out:
> > static int powernowk8_cpu_exit(struct cpufreq_policy *pol)
> > {
> > struct powernow_k8_data *data = per_cpu(powernow_data, pol->cpu);
> > + int cpu;
> >
> > if (!data)
> > return -EINVAL;
> > @@ -1165,7 +1168,8 @@ static int powernowk8_cpu_exit(struct cpufreq_policy *pol)
> >
> > kfree(data->powernow_table);
> > kfree(data);
> > - per_cpu(powernow_data, pol->cpu) = NULL;
> > + for_each_cpu(cpu, pol->cpus)
> > + per_cpu(powernow_data, cpu) = NULL;
> >
> > return 0;
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Queued up as a fix for 3.14, thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-02-17 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 10:48 Srivatsa S. Bhat
2014-02-17 11:05 ` Viresh Kumar
2014-02-17 22:02 ` Rafael J. Wysocki [this message]
2014-02-18 2:06 ` Viresh Kumar
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=1851033.kRQPL2X90T@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pierre-list@ossman.eu \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®