From: "Li, Aubrey" <aubrey.li@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Brown, Len" <len.brown@intel.com>,
"alan@linux.intel.com" <alan@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
"linux-pm@vger.kernel.org >> Linux PM list"
<linux-pm@vger.kernel.org>
Subject: Re: [PATCH v2] PM / Sleep: Timer quiesce in freeze state
Date: Fri, 14 Nov 2014 15:58:13 +0800 [thread overview]
Message-ID: <5465B615.8090203@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1411131405370.3935@nanos>
On 2014/11/13 21:06, Thomas Gleixner wrote:
> On Thu, 13 Nov 2014, Li, Aubrey wrote:
>
>> On 2014/11/13 17:10, Thomas Gleixner wrote:
>>> On Thu, 13 Nov 2014, Peter Zijlstra wrote:
>>>> On Wed, Nov 12, 2014 at 10:09:47PM +0100, Thomas Gleixner wrote:
>>>> But sure, we can add suspend notifiers to stuff to shut down timers; I
>>>> should have a patch for at least one of the offenders somewhere. But I
>>>> really think that we should not be looking at the individual timers for
>>>> this, none of the other suspend modes care about active timers.
>>>
>>> Fair enough.
>>>
>>
>> If you are okay with the current method to suspend timekeeping entirely,
>> then we can go further to fix the rest concerns.
>
> I'm fine with that when it's done proper :)
>
Sure, thanks for the suggestion, let me try my best to make you happy, ;)
> Thanks,
>
> tglx
>
>
next prev parent reply other threads:[~2014-11-14 7:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 15:15 [RFC/PATCH] PM / Sleep: Timer quiesce in freeze state Li, Aubrey
2014-10-24 15:36 ` Peter Zijlstra
2014-10-27 6:27 ` Li, Aubrey
2014-10-27 7:28 ` Peter Zijlstra
2014-10-28 4:32 ` Li, Aubrey
2014-10-28 8:29 ` Peter Zijlstra
2014-10-28 22:46 ` Li, Aubrey
2014-10-29 8:21 ` Peter Zijlstra
2014-10-29 15:09 ` Li, Aubrey
2014-10-27 7:44 ` Peter Zijlstra
2014-10-28 7:52 ` Li, Aubrey
2014-10-28 8:25 ` Peter Zijlstra
2014-10-28 23:22 ` Li, Aubrey
2014-10-29 8:24 ` Peter Zijlstra
2014-10-30 2:58 ` [PATCH v2] " Li, Aubrey
2014-11-08 2:05 ` Rafael J. Wysocki
2014-11-10 11:49 ` Peter Zijlstra
2014-11-12 21:09 ` Thomas Gleixner
2014-11-13 1:37 ` Peter Zijlstra
2014-11-13 2:20 ` Li, Aubrey
2014-11-13 9:19 ` Thomas Gleixner
2014-11-13 10:50 ` Li, Aubrey
2014-11-13 9:10 ` Thomas Gleixner
2014-11-13 10:47 ` Li, Aubrey
2014-11-13 13:06 ` Thomas Gleixner
2014-11-14 7:58 ` Li, Aubrey [this message]
2014-10-28 4:39 ` [RFC/PATCH] " Li, Aubrey
2014-10-28 8:25 ` Peter Zijlstra
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=5465B615.8090203@linux.intel.com \
--to=aubrey.li@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
/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.