diff options
| author |  Frederic Weisbecker <frederic@kernel.org>
| 2020-12-02 12:57:32 +0100 |
|---|---|---|
| committer |  Thomas Gleixner <tglx@linutronix.de>
| 2020-12-02 20:20:05 +0100 |
| commit | d14ce74f1fb376ccbbc0b05ded477ada51253729 (patch) | |
| tree | 4458ca24e001e08e17815d169d1266690c02cd2a /arch | |
| parent | irqtime: Move irqtime entry accounting after irq offset incrementation (diff) | |
| download | linux-d14ce74f1fb376ccbbc0b05ded477ada51253729.tar.gz linux-d14ce74f1fb376ccbbc0b05ded477ada51253729.tar.bz2 linux-d14ce74f1fb376ccbbc0b05ded477ada51253729.zip | |
irq: Call tick_irq_enter() inside HARDIRQ_OFFSET
Now that account_hardirq_enter() is called after HARDIRQ_OFFSET has
been incremented, there is nothing left that prevents us from also
moving tick_irq_enter() after HARDIRQ_OFFSET is incremented.
The desired outcome is to remove the nasty hack that prevents softirqs
from being raised through ksoftirqd instead of the hardirq bottom half.
Also tick_irq_enter() then becomes appropriately covered by lockdep.
Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20201202115732.27827-6-frederic@kernel.org
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions