From: "Li, Aubrey" <aubrey.li@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Brown, Len" <len.brown@intel.com>,
"alan@linux.intel.com" <alan@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"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: [RFC/PATCH] PM / Sleep: Timer quiesce in freeze state
Date: Tue, 28 Oct 2014 12:32:16 +0800 [thread overview]
Message-ID: <544F1C50.8010505@linux.intel.com> (raw)
In-Reply-To: <20141027072816.GD10501@worktop.programming.kicks-ass.net>
On 2014/10/27 15:28, Peter Zijlstra wrote:
> On Mon, Oct 27, 2014 at 02:27:27PM +0800, Li, Aubrey wrote:
>>> Now I suppose the problem is with cpu_pause() which needs IPIs to
>>> complete? Do we really need cpuidle_pause() there?
>>> cpuidle_uninstall_handlers() seems like a daft thing to call just about
>>> there.
>>
>> Please check the log of 8651f97bd951d0bb1c10fa24e3fa3455193f3548.
>> Rafael should know more this question than me.
>
> That changelog explains its complete bollocks to do it here. We _want_
> to enter and/or remain in deep idle states.
cpuidle_resume() will be called at the end of dpm_resume_noirq(). So we
still are able to enter deep idle states after resume.
Thanks,
-Aubrey
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2014-10-28 4:32 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 [this message]
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
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=544F1C50.8010505@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.