[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1612151143-72242-1-git-send-email-chenshiyan@linux.alibaba.com>
Date: Mon, 1 Feb 2021 11:45:43 +0800
From: chenshiyan <chenshiyan@...ux.alibaba.com>
To: fweisbec@...il.com, tglx@...utronix.de, mingo@...nel.org,
torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: [PATCH RESEND] nohz: Restart tick before do softirq
When the cpu is continuously idle, tick_irq_exit() will count next tick
expiry with maybe several periodic ticks, but if it enters softirq
before next tick, invoke_softirq() is called before tick_irq_exit(),
there will be no ticks during softirq. So with sched_clock_irqtime
closing, sirq is very low in nohz idle even if the softirq costs much
time beause of the sampling ticks missing(sirq will be much higher and
seem exact if the cpu is busy).
Signed-off-by: chenshiyan <chenshiyan@...ux.alibaba.com>
---
kernel/softirq.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/softirq.c b/kernel/softirq.c
index 9d71046..8f3f71b9 100644
--- a/kernel/softirq.c
+++ b/kernel/softirq.c
@@ -210,6 +210,7 @@ static inline void invoke_softirq(void)
return;
if (!force_irqthreads) {
+ tick_nohz_idle_restart_tick();
#ifdef CONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK
/*
* We can safely execute softirq on the current stack if
--
1.8.3.1
Powered by blists - more mailing lists