cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	cpufreq@vger.kernel.org, Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: 3.10-rcX: cpu governor ondemand doesn't scale well after s2ram
Date: Sat, 29 Jun 2013 19:50:11 +0200	[thread overview]
Message-ID: <51CF1E53.6060902@gmx.de> (raw)
In-Reply-To: <CAKohpok1gThXL925Yz5UgC54vTVQgymBA1cLGER_g-dgZu0JLA@mail.gmail.com>

The latest bisect attempt gave :

commit a66b2e503fc79fff6632d02ef5a0ee47c1d2553d
Author: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
Date:   Wed May 15 21:47:17 2013 +0200

    cpufreq: Preserve sysfs files across suspend/resume

    The file permissions of cpufreq per-cpu sysfs files are not preserved
    across suspend/resume because we internally go through the CPU
    Hotplug path which reinitializes the file permissions on CPU online.

    But the user is not supposed to know that we are using CPU hotplug
    internally within suspend/resume (IOW, the kernel should not silently
    wreck the user-set file permissions across a suspend cycle).
    Therefore, we need to preserve the file permissions as they are
    across suspend/resume.

    The simplest way to achieve that is to just not touch the sysfs files
    at all - ie., just ignore the CPU hotplug notifications in the
    suspend/resume path (_FROZEN) in the cpufreq hotplug callback.

    Reported-by: Robert Jarzmik <robert.jarzmik@intel.com>
    Reported-by: Durgadoss R <durgadoss.r@intel.com>
    Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
    Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>



To get a more reliable bisect result I had to start BOINC before (4
childs each with nice -19 started)

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

  reply	other threads:[~2013-06-29 17:50 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 15:57 3.10-rcX: cpu governor ondemand doesn't scale well after s2ram Toralf Förster
2013-06-18 20:27 ` Toralf Förster
2013-06-18 22:05 ` Rafael J. Wysocki
2013-06-26 18:36   ` Toralf Förster
2013-06-26 19:12     ` Rafael J. Wysocki
2013-06-27  4:10       ` Viresh Kumar
2013-06-27 18:00         ` Toralf Förster
2013-06-28  3:44           ` Viresh Kumar
2013-06-28 15:25             ` Toralf Förster
2013-06-29 13:30               ` Viresh Kumar
2013-06-29 17:50                 ` Toralf Förster [this message]
2013-06-30 14:22                   ` Rafael J. Wysocki
2013-06-30 15:15                     ` Viresh Kumar
2013-06-30 16:20                       ` Toralf Förster
2013-06-30 16:21                       ` Toralf Förster
2013-06-30 16:33                     ` Srivatsa S. Bhat
2013-06-30 17:05                       ` Toralf Förster
2013-06-30 18:52                         ` [PATCH] cpufreq: Fix cpufreq regression after suspend/resume Srivatsa S. Bhat
2013-06-30 22:46                           ` Rafael J. Wysocki
2013-07-10 20:50                           ` Toralf Förster
2013-07-10 22:29                             ` Srivatsa S. Bhat
2013-07-11  5:40                               ` Lan Tianyu
2013-07-11  6:23                                 ` Srivatsa S. Bhat
2013-07-11 14:03                                   ` Lan Tianyu
2013-07-11 14:24                                     ` Srivatsa S. Bhat
2013-07-11 14:23                                   ` Alan Stern
2013-07-11 14:38                                     ` Srivatsa S. Bhat
2013-07-13 10:16                             ` Paul Bolle
2013-07-13 12:52                               ` Paul Bolle
2013-07-15  6:13                                 ` Srivatsa S. Bhat
2013-07-03 19:46                         ` 3.10-rcX: cpu governor ondemand doesn't scale well after s2ram Toralf Förster
2013-07-04  6:55                           ` Srivatsa S. Bhat
2013-07-04  7:01                             ` Viresh Kumar
2013-07-04  7:08                               ` Srivatsa S. Bhat
2013-07-04  7:58                                 ` Viresh Kumar
2013-07-10 19:31                                   ` Toralf Förster
2013-07-04  8:04                                 ` Viresh Kumar
2013-07-04  8:23                                   ` Viresh Kumar
2013-07-04 16:42                                     ` Toralf Förster
2013-07-05  4:35                                       ` Viresh Kumar
2013-07-05 14:06                                         ` Toralf Förster
2013-06-28 17:17             ` Toralf Förster
2013-06-28 18:56               ` Rafael J. Wysocki
2013-06-28 18:51                 ` Toralf Förster

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=51CF1E53.6060902@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=cpufreq@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --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;
as well as URLs for NNTP newsgroup(s).