Add cpuidle-powernv upstream bug fixes and upstream patch to fix kernel regression due to cpuidle on to 14.04.03 kernel

[bugproxy]

This is a feature request to include the following patches in 14.04.03 kernel.

[1] 74aa51b5ccd39753 cpuidle: powernv: Populate cpuidle state details by querying the device-tree
(3.18 upstream)

[2] cpuidle/powernv: Read target_residency value of idle states from DT if available
https://lkml.org/lkml/2015/2/3/23

[3] tick/broadcast-hrtimer : Fix suspicious RCU usage in idle loop
http://linuxppc.10917.n7.nabble.com/PATCH-tick-broadcast-hrtimer-Fix-suspicious-RCU-usage-in-idle-loop-td89675.html

[1] and [2] patches provide fixes to read the latency and target_residency values of different idle states from the device tree if they are present in the device tree. This fix will avoid cpu from aggressively entering into fastsleep.

[3] is an important fix against a kernel regression down the cpuidle path which was reported in the community.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1451825/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Chris J Arges (arges)]

So just for clarification, when you mention 14.04.3 you mean the v3.19 series kernel.
If this is the case then only two patches are required:

commit 92c83ff5b42b109c94fdeee53cb31f674f776d75
commit a127d2bcf1fbc8c8e0b5cf0dab54f7d3ff50ce47

[Chris J Arges (arges)]

bug 1435951 is a duplicate of this bug and the patches are already in vivid, therefore they will be in the lts-vivid kernel in 14.04.3

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-05-07 13:02 EDT-------
(In reply to comment #6)
> So just for clarification, when you mention 14.04.3 you mean the v3.19
> series kernel.
> If this is the case then only two patches are required:
>
> commit 92c83ff5b42b109c94fdeee53cb31f674f776d75
> commit a127d2bcf1fbc8c8e0b5cf0dab54f7d3ff50ce47

Yes. But both of them are back ported to 15.04.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-05-26 13:21 EDT-------
Admin Changes