Messages in this thread | | | Date | Tue, 22 Jul 2014 15:21:10 -0700 | From | Stephen Boyd <> | Subject | Re: [PATCH] sched_clock: Avoid corrupting hrtimer tree during suspend |
| |
On 07/18/14 17:14, John Stultz wrote: > On 07/18/2014 04:24 PM, Stephen Boyd wrote: >> On 07/18/14 15:42, John Stultz wrote: >>> If its a regression (and needs -stable backports) it needs to go in via >>> tip/timers/urgent, and not via the regular merge window. >>> >>> Whats the additional risk -stable wise for canceling the timer during >>> suspend and starting it back up during resume? >>> >> I'd say close to zero given that we'd only be making the timer run a >> little bit later and we have slack in there already. Here's that version. > Ok, thanks. I'll try to do a closer review it and get it queued. Is > there anyone who might be able to validate this and provide a Tested-by: ? >
Maybe someone from Linaro can give a Tested-by? I basically did this:
# grep -A1 'sched_clock' /proc/timer_list && echo mem > /sys/power/state && grep -A1 'sched_clock' /proc/timer_list
and made sure that the expires time was reset.
-- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
| |