On Mon, May 6, 2013 at 4:01 PM, Pavel Machek wrote:
> Hi!
>
>> - suspend/resume enhancements by Feng Tang: on certain new Intel Atom
>>processors (Penwell and Cloverview), there is a feature that the TSC
>>won't stop in S3 state, so the TSC value won't be reset to 0 after
>>resume. Th
Hi!
> - suspend/resume enhancements by Feng Tang: on certain new Intel Atom
>processors (Penwell and Cloverview), there is a feature that the TSC
>won't stop in S3 state, so the TSC value won't be reset to 0 after
>resume. This can be taken advantage of by the generic via the
>C
On Tue, 30 Apr 2013, Linus Torvalds wrote:
> Both sets of patches were done by Thomas, and I *really* want you guys
> to take a look at my conflict resolution. I effectively moved the new
> "don't go into deep idle if boradcast timer is pending" check from x86
> and arm into the generic idle loop.
* Linus Torvalds wrote:
> On Tue, Apr 30, 2013 at 12:43 AM, Ingo Molnar wrote:
> >
> > Please pull the latest timers-core-for-linus git tree from:
> >
> >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> > timers-core-for-linus
>
> Hmm.. The "Use generic idle loop" patches from
On Tue, Apr 30, 2013 at 12:43 AM, Ingo Molnar wrote:
>
> Please pull the latest timers-core-for-linus git tree from:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> timers-core-for-linus
Hmm.. The "Use generic idle loop" patches from the SMP/hotplug pull
conflicted with the "U
5 matches
Mail list logo