Re: [PATCH] Trace idle entry and exit times

2013-12-07 Thread Andi Kleen
> > Well that one is obvious. I mean more the subtle problems. > > Yeah, not subtle. SGI could use C2 as power supply stress tester. This is only on system where the APIC timer does not tick in deep idle. At this point these are 5+ year old systems. There were some ideas of breaking up that loc

Re: [PATCH] Trace idle entry and exit times

2013-12-07 Thread Mike Galbraith
On Sat, 2013-12-07 at 06:20 +0100, Andi Kleen wrote: > On Sat, Dec 07, 2013 at 05:57:32AM +0100, Mike Galbraith wrote: > > On Fri, 2013-12-06 at 16:46 -0800, Andi Kleen wrote: > > > From: Andi Kleen > > > > > > This patch creates 4 new trace points: one at the beginning of idle, > > > one befor

Re: [PATCH] Trace idle entry and exit times

2013-12-06 Thread Andi Kleen
On Sat, Dec 07, 2013 at 05:57:32AM +0100, Mike Galbraith wrote: > On Fri, 2013-12-06 at 16:46 -0800, Andi Kleen wrote: > > From: Andi Kleen > > > > This patch creates 4 new trace points: one at the beginning of idle, > > one before entering mwait, one after exiting mwait, and one after > > finis

Re: [PATCH] Trace idle entry and exit times

2013-12-06 Thread Mike Galbraith
On Fri, 2013-12-06 at 16:46 -0800, Andi Kleen wrote: > From: Andi Kleen > > This patch creates 4 new trace points: one at the beginning of idle, > one before entering mwait, one after exiting mwait, and one after > finishing the idle code. This is useful to trace down any > additional latencies

[PATCH] Trace idle entry and exit times

2013-12-06 Thread Andi Kleen
From: Andi Kleen This patch creates 4 new trace points: one at the beginning of idle, one before entering mwait, one after exiting mwait, and one after finishing the idle code. This is useful to trace down any additional latencies caused by the ever-growing idle code. Idle latencies are a common