Re: [RFC PATCH 22/22 -v2] Trace irq disabled critical timings

2008-01-10 Thread Steven Rostedt
On Wed, 9 Jan 2008, Daniel Walker wrote: > > On Wed, 2008-01-09 at 18:29 -0500, Steven Rostedt wrote: > > + /* Don't trace irqs off for idle */ > > + stop_critical_timings(); > > idle(); > > + start_critical_t

Re: [RFC PATCH 22/22 -v2] Trace irq disabled critical timings

2008-01-09 Thread Daniel Walker
On Wed, 2008-01-09 at 18:29 -0500, Steven Rostedt wrote: > + /* Don't trace irqs off for idle */ > + stop_critical_timings(); > idle(); > + start_critical_timings(); Is there another way to hook into the id

[RFC PATCH 22/22 -v2] Trace irq disabled critical timings

2008-01-09 Thread Steven Rostedt
This patch adds latency tracing for critical timings. In /debugfs/tracing/ three files are added: max_irq_latency holds the max latency thus far (in usecs) (default to large number so one must start latency tracing) irq_thresh threshold (in usecs) to always print out if irqs off