Re: [PATCH V7] irq: Track the interrupt timings

2016-06-23 Thread Daniel Lezcano
On 06/23/2016 12:12 PM, Thomas Gleixner wrote: On Thu, 23 Jun 2016, Daniel Lezcano wrote: On 06/23/2016 10:41 AM, Thomas Gleixner wrote: Is it really required to do this per interrupt rather than providing per cpu statistics of interrupts which arrived in the last X seconds or whatever timefram

Re: [PATCH V7] irq: Track the interrupt timings

2016-06-23 Thread Thomas Gleixner
On Thu, 23 Jun 2016, Daniel Lezcano wrote: > On 06/23/2016 10:41 AM, Thomas Gleixner wrote: > > Is it really required to do this per interrupt rather than providing per cpu > > statistics of interrupts which arrived in the last X seconds or whatever > > timeframe is relevant for this. > > Perhaps

Re: [PATCH V7] irq: Track the interrupt timings

2016-06-23 Thread Daniel Lezcano
On 06/23/2016 10:41 AM, Thomas Gleixner wrote: On Fri, 17 Jun 2016, Daniel Lezcano wrote: The interrupt framework gives a lot of information about each interrupt. It does not keep track of when those interrupts occur though. This patch provides a mean to record the elapsed time between success

Re: [PATCH V7] irq: Track the interrupt timings

2016-06-23 Thread Thomas Gleixner
On Fri, 17 Jun 2016, Daniel Lezcano wrote: > The interrupt framework gives a lot of information about each interrupt. > > It does not keep track of when those interrupts occur though. > > This patch provides a mean to record the elapsed time between successive > interrupt occurrences in a per-IRQ

[PATCH V7] irq: Track the interrupt timings

2016-06-17 Thread Daniel Lezcano
The interrupt framework gives a lot of information about each interrupt. It does not keep track of when those interrupts occur though. This patch provides a mean to record the elapsed time between successive interrupt occurrences in a per-IRQ per-CPU circular buffer to help with the prediction of