From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: viresh.kumar@linaro.org, toralf.foerster@gmx.de,
robert.jarzmik@intel.com, durgadoss.r@intel.com,
tianyu.lan@intel.com, lantianyu1986@gmail.com,
dirk.brandewie@gmail.com, stern@rowland.harvard.edu,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] Cpufreq, cpu hotplug, suspend/resume related fixes
Date: Fri, 12 Jul 2013 03:53:55 +0530 [thread overview]
Message-ID: <51DF307B.7060307@linux.vnet.ibm.com> (raw)
In-Reply-To: <6515593.XAmN11qlGF@vostro.rjw.lan>
On 07/12/2013 04:03 AM, Rafael J. Wysocki wrote:
> On Friday, July 12, 2013 03:45:17 AM Srivatsa S. Bhat wrote:
>>
>> Hi,
>
> Hi,
>
>> Commit a66b2e (cpufreq: Preserve sysfs files across suspend/resume) caused
>> some subtle regressions in the cpufreq subsystem during suspend/resume.
>> This patchset is aimed at rectifying those problems, by fixing the regression
>> as well as achieving the original goal of that commit in a proper way.
>>
>> Patch 1 reverts the above commit, and is CC'ed to stable.
>>
>> Patches 2 - 5 reorganize the code and have no functional impact, and can go
>> in as general cleanups as well. This reorganization builds a base that the
>> rest of the patches will make use of.
>>
>> Patch 6 and 7 add a mechanism to perform light-weight init/tear-down of CPUs
>> in the cpufreq subsystem and finally patch 8 uses it to preserve sysfs files
>> across suspend/resume.
>>
>> All the patches apply on current mainline.
>>
>>
>> Robert, Durgadoss, it would be great if you could try it out and see if it works
>> well for your usecase. I tested it locally and cpufreq related files did retain
>> their permissions across suspend/resume. Let me know if it works fine in your
>> setup too.
>>
>> And I'd of course appreciate to hear from Dirk, Tianyu and Toralf to know
>> whether their systems work fine after:
>> a. applying only the first commit (this is what gets backported to stable)
>> b. applying all the commits
>>
>> (Note: I had to use Michael's fix[1] to avoid CPU hotplug deadlock while
>> testing this patchset. Though that patch also touches cpufreq subsystem, it
>> doesn't affect this patchset in any way and there is absolutely no dependency
>> between the two in terms of code. That fix just makes basic CPU hotplug work
>> without locking up on current mainline).
>>
>> [1]. https://lkml.org/lkml/2013/7/10/611
>>
>>
>> Thank you very much!
>
> Thanks Srivatsa!
>
> I'm going to take [1/8] for 3.11 and queue up the rest for 3.12 if people don't
> hate them. This way we'll have some more testing coverage before they reach
> the mainline hopefully.
>
Sounds great! Thanks a lot Rafael!
Regards,
Srivatsa S. Bhat
next prev parent reply other threads:[~2013-07-11 22:23 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 22:15 [PATCH 0/8] Cpufreq, cpu hotplug, suspend/resume related fixes Srivatsa S. Bhat
2013-07-11 22:15 ` [PATCH 1/8] cpufreq: Revert commit a66b2e to fix cpufreq regression during suspend/resume Srivatsa S. Bhat
2013-07-12 7:18 ` Viresh Kumar
2013-07-13 12:46 ` Paul Bolle
2013-07-15 6:18 ` Srivatsa S. Bhat
2013-07-11 22:15 ` [PATCH 2/8] cpufreq: Fix misplaced call to cpufreq_update_policy() Srivatsa S. Bhat
2013-07-12 7:06 ` Viresh Kumar
2013-07-15 6:20 ` Srivatsa S. Bhat
2013-07-15 11:37 ` Rafael J. Wysocki
2013-07-11 22:16 ` [PATCH 3/8] cpufreq: Add helper to perform alloc/free of policy structure Srivatsa S. Bhat
2013-07-12 7:09 ` Viresh Kumar
2013-07-15 6:24 ` Srivatsa S. Bhat
2013-07-11 22:16 ` [PATCH 4/8] cpufreq: Extract non-interface related stuff from cpufreq_add_dev_interface Srivatsa S. Bhat
2013-07-12 7:17 ` Viresh Kumar
2013-07-11 22:16 ` [PATCH 5/8] cpufreq: Extract the handover of policy cpu to a helper function Srivatsa S. Bhat
2013-07-12 7:19 ` Viresh Kumar
2013-07-11 22:16 ` [PATCH 6/8] cpufreq: Introduce a flag ('frozen') to separate full vs temporary init/teardown Srivatsa S. Bhat
2013-07-12 7:31 ` Viresh Kumar
2013-07-11 22:17 ` [PATCH 7/8] cpufreq: Preserve policy structure across suspend/resume Srivatsa S. Bhat
2013-07-15 9:55 ` Viresh Kumar
2013-07-15 10:05 ` Srivatsa S. Bhat
2013-07-15 10:21 ` Viresh Kumar
2013-07-15 11:52 ` Srivatsa S. Bhat
2013-07-15 11:35 ` Rafael J. Wysocki
2013-07-15 11:53 ` Srivatsa S. Bhat
2013-07-16 6:15 ` Viresh Kumar
2013-07-16 8:56 ` Srivatsa S. Bhat
2013-07-16 9:10 ` Viresh Kumar
2013-07-16 9:29 ` Srivatsa S. Bhat
2013-07-16 9:35 ` Viresh Kumar
2013-07-16 9:54 ` Srivatsa S. Bhat
2013-07-11 22:17 ` [PATCH 8/8] cpufreq: Perform light-weight init/teardown during suspend/resume Srivatsa S. Bhat
2013-07-11 22:25 ` [PATCH 0/8] Cpufreq, cpu hotplug, suspend/resume related fixes Jarzmik, Robert
2013-07-11 22:33 ` Rafael J. Wysocki
2013-07-11 22:23 ` Srivatsa S. Bhat [this message]
2013-07-16 15:15 ` Toralf Förster
2013-07-16 21:32 ` Rafael J. Wysocki
2013-07-17 5:03 ` Srivatsa S. Bhat
2013-07-17 15:27 ` Toralf Förster
2013-07-17 15:49 ` Srivatsa S. Bhat
2013-07-21 8:43 ` Srivatsa S. Bhat
2013-07-21 9:40 ` Toralf Förster
2013-07-21 10:38 ` Srivatsa S. Bhat
2013-07-21 12:59 ` Rafael J. Wysocki
2013-07-15 17:38 ` Toralf Förster
2013-07-15 23:25 ` Rafael J. Wysocki
2013-07-13 9:23 ` Toralf Förster
2013-07-13 13:50 ` Toralf Förster
2013-07-15 6:40 ` Srivatsa S. Bhat
2013-07-15 8:27 ` Lan Tianyu
2013-07-15 8:43 ` Srivatsa S. Bhat
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=51DF307B.7060307@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=dirk.brandewie@gmail.com \
--cc=durgadoss.r@intel.com \
--cc=lantianyu1986@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=robert.jarzmik@intel.com \
--cc=stern@rowland.harvard.edu \
--cc=tianyu.lan@intel.com \
--cc=toralf.foerster@gmx.de \
--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).