public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 3.15-rc2: longhaul cpufreq stalls tasks for 120s+
Date: Thu, 24 Apr 2014 14:17:29 +0300 (EEST)	[thread overview]
Message-ID: <alpine.SOC.1.00.1404241417120.13595@math.ut.ee> (raw)
In-Reply-To: <CAKohpo=Lzzj5eki3644-ESB+P39+Q-ARFqN-S+_HM5UB802W3g@mail.gmail.com>

> On 24 April 2014 15:46, Meelis Roos <mroos@linux.ee> wrote:
> > I can add debug to where needed and try it.
> 
> I am quite sure below wouldn't fix it, but just wanted to check
> for the corner case :(
> 
> Can you please try attached patch (mail's content would be
> broken):

Did not help. Will try lock debugging now.

> 
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index abda660..7198e23 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -355,10 +355,12 @@ void cpufreq_freq_transition_begin(struct
> cpufreq_policy *policy,
>                 struct cpufreq_freqs *freqs)
>  {
>  wait:
> +       smp_mb();
>         wait_event(policy->transition_wait, !policy->transition_ongoing);
> 
>         spin_lock(&policy->transition_lock);
> 
> +       smp_mb();
>         if (unlikely(policy->transition_ongoing)) {
>                 spin_unlock(&policy->transition_lock);
>                 goto wait;
> @@ -380,8 +382,11 @@ void cpufreq_freq_transition_end(struct
> cpufreq_policy *policy,
> 
>         cpufreq_notify_post_transition(policy, freqs, transition_failed);
> 
> +       smp_mb();
> +
>         policy->transition_ongoing = false;
> 
> +       smp_mb();
>         wake_up(&policy->transition_wait);
>  }
>  EXPORT_SYMBOL_GPL(cpufreq_freq_transition_end);
> 

-- 
Meelis Roos (mroos@linux.ee)

  reply	other threads:[~2014-04-24 11:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  9:56 3.15-rc2: longhaul cpufreq stalls tasks for 120s+ Meelis Roos
2014-04-24 10:10 ` Viresh Kumar
2014-04-24 10:16   ` Meelis Roos
2014-04-24 10:29     ` Viresh Kumar
2014-04-24 11:17       ` Meelis Roos [this message]
2014-04-24 10:47     ` Srivatsa S. Bhat
2014-04-24 19:03       ` Meelis Roos
2014-04-24 19:44         ` Srivatsa S. Bhat
2014-04-25  6:44           ` Viresh Kumar
2014-04-25  4:41         ` Viresh Kumar
2014-04-25  8:15           ` Srivatsa S. Bhat
2014-04-25  7:31 ` 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=alpine.SOC.1.00.1404241417120.13595@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=cpufreq@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --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