diff options
author | 2020-12-02 12:57:31 +0100 | |
---|---|---|
committer | 2020-12-02 20:20:05 +0100 | |
commit | d3759e7184f8f6187e62f8c4e7dcb1f6c47c075a (patch) | |
tree | 0c83a96f3b76385bcda96eb4eadf82377dfc28e7 /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | sched/vtime: Consolidate IRQ time accounting (diff) | |
download | wireguard-linux-d3759e7184f8f6187e62f8c4e7dcb1f6c47c075a.tar.xz wireguard-linux-d3759e7184f8f6187e62f8c4e7dcb1f6c47c075a.zip |
irqtime: Move irqtime entry accounting after irq offset incrementation
IRQ time entry is currently accounted before HARDIRQ_OFFSET or
SOFTIRQ_OFFSET are incremented. This is convenient to decide to which
index the cputime to account is dispatched.
Unfortunately it prevents tick_irq_enter() from being called under
HARDIRQ_OFFSET because tick_irq_enter() has to be called before the IRQ
entry accounting due to the necessary clock catch up. As a result we
don't benefit from appropriate lockdep coverage on tick_irq_enter().
To prepare for fixing this, move the IRQ entry cputime accounting after
the preempt offset is incremented. This requires the cputime dispatch
code to handle the extra offset.
Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lore.kernel.org/r/20201202115732.27827-5-frederic@kernel.org
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions