From: john.stultz@linaro.org (John Stultz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] sched_clock: Avoid corrupting hrtimer tree during suspend
Date: Fri, 18 Jul 2014 17:14:26 -0700 [thread overview]
Message-ID: <53C9B862.5050106@linaro.org> (raw)
In-Reply-To: <53C9ACCA.3070306@codeaurora.org>
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: ?
thanks
-john
WARNING: multiple messages have this Message-ID (diff)
From: John Stultz <john.stultz@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] sched_clock: Avoid corrupting hrtimer tree during suspend
Date: Fri, 18 Jul 2014 17:14:26 -0700 [thread overview]
Message-ID: <53C9B862.5050106@linaro.org> (raw)
In-Reply-To: <53C9ACCA.3070306@codeaurora.org>
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: ?
thanks
-john
next prev parent reply other threads:[~2014-07-19 0:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 22:09 [PATCH] sched_clock: Avoid corrupting hrtimer tree during suspend Stephen Boyd
2014-07-18 22:09 ` Stephen Boyd
2014-07-18 22:25 ` John Stultz
2014-07-18 22:25 ` John Stultz
2014-07-18 22:38 ` Stephen Boyd
2014-07-18 22:38 ` Stephen Boyd
2014-07-18 22:42 ` John Stultz
2014-07-18 22:42 ` John Stultz
2014-07-18 23:24 ` Stephen Boyd
2014-07-18 23:24 ` Stephen Boyd
2014-07-19 0:14 ` John Stultz [this message]
2014-07-19 0:14 ` John Stultz
2014-07-22 22:21 ` Stephen Boyd
2014-07-22 22:21 ` Stephen Boyd
-- strict thread matches above, loose matches on Subject: below --
2014-07-24 4:03 John Stultz
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=53C9B862.5050106@linaro.org \
--to=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.