On Mon, 17 Jul 2017, Arjan van de Ven wrote: > On 7/17/2017 12:46 PM, Thomas Gleixner wrote: > > That's where Daniel Lezcanos work of predicting interrupts comes in and > > that's the right solution to the problem. The core infrastructure has been > > merged, just the idle/cpufreq users are not there yet. All you need to do > > is to select CONFIG_IRQ_TIMINGS and use the statistics generated there. > > > yes ;-)
:) > also note that the predictor does not need to perfect, on most systems C > states are an order of magnitude apart in terms of > power/performance/latency so if you get the general order of magnitude > right the predictor is doing its job. So it would be interesting just to enable the irq timings stuff and compare the outcome as a first step. That should be reasonably simple to implement and would give us also some information of how that code behaves on larger systems. Thanks, tglx