From: Marco Crivellari <marco.crivellari@suse.com>
To: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Marco Crivellari <marco.crivellari@suse.com>,
Frederic Weisbecker <frederic@kernel.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Huacai Chen <chenhuacai@kernel.org>,
"Maciej W . Rozycki" <macro@orcam.me.uk>
Subject: [PATCH v6 1/1] MIPS: Fix idle VS timer enqueue
Date: Sat, 15 Mar 2025 20:40:02 +0100 [thread overview]
Message-ID: <20250315194002.13778-2-marco.crivellari@suse.com> (raw)
In-Reply-To: <20250315194002.13778-1-marco.crivellari@suse.com>
MIPS re-enables interrupts on its idle routine and performs
a TIF_NEED_RESCHED check afterwards before putting the CPU to sleep.
The IRQs firing between the check and the 'wait' instruction may set the
TIF_NEED_RESCHED flag. In order to deal with this possible race, IRQs
interrupting __r4k_wait() rollback their return address to the
beginning of __r4k_wait() so that TIF_NEED_RESCHED is checked
again before going back to sleep.
However idle IRQs can also queue timers that may require a tick
reprogramming through a new generic idle loop iteration but those timers
would go unnoticed here because __r4k_wait() only checks
TIF_NEED_RESCHED. It doesn't check for pending timers.
Fix this with fast-forwarding idle IRQs return address to the end of the
idle routine instead of the beginning, so that the generic idle loop
handles both TIF_NEED_RESCHED and pending timers.
CONFIG_CPU_MICROMIPS has been removed along with the nop instructions.
There, NOPs are 2 byte in size, so change the code with 3 _ssnop which are
always 4 byte and remove the ifdef. Added ehb to make sure the hazard
is always cleared.
Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
---
arch/mips/kernel/genex.S | 42 ++++++++++++++++++++++------------------
arch/mips/kernel/idle.c | 1 -
2 files changed, 23 insertions(+), 20 deletions(-)
diff --git a/arch/mips/kernel/genex.S b/arch/mips/kernel/genex.S
index a572ce36a24f..4e012421d00f 100644
--- a/arch/mips/kernel/genex.S
+++ b/arch/mips/kernel/genex.S
@@ -104,27 +104,30 @@ handle_vcei:
__FINIT
- .align 5 /* 32 byte rollback region */
+ .align 5
LEAF(__r4k_wait)
.set push
.set noreorder
- /* start of rollback region */
- LONG_L t0, TI_FLAGS($28)
- nop
- andi t0, _TIF_NEED_RESCHED
- bnez t0, 1f
- nop
- nop
- nop
-#ifdef CONFIG_CPU_MICROMIPS
- nop
- nop
- nop
- nop
-#endif
+ /* Start of idle interrupt region. */
+ MFC0 t0, CP0_STATUS
+ /* Enable interrupt. */
+ ori t0, 0x1f
+ xori t0, 0x1e
+ MTC0 t0, CP0_STATUS
+ _ssnop
+ _ssnop
+ _ssnop
+ _ehb
.set MIPS_ISA_ARCH_LEVEL_RAW
+ /*
+ * If an interrupt lands here, between enabling interrupts above and
+ * going idle on the next instruction, we must *NOT* go idle since the
+ * interrupt could have set TIF_NEED_RESCHED or caused a timer to need
+ * resched. Fall through -- see rollback_handler below -- and have
+ * the idle loop take care of things.
+ */
wait
- /* end of rollback region (the region size must be power of two) */
+ /* End of idle interrupt region. */
1:
jr ra
nop
@@ -136,9 +139,10 @@ LEAF(__r4k_wait)
.set push
.set noat
MFC0 k0, CP0_EPC
- PTR_LA k1, __r4k_wait
- ori k0, 0x1f /* 32 byte rollback region */
- xori k0, 0x1f
+ PTR_LA k1, 1b
+ /* 36 byte idle interrupt region. */
+ ori k0, 0x1f
+ PTR_ADDIU k0, 5
bne k0, k1, \handler
MTC0 k0, CP0_EPC
.set pop
diff --git a/arch/mips/kernel/idle.c b/arch/mips/kernel/idle.c
index 5abc8b7340f8..1f74c0589f7e 100644
--- a/arch/mips/kernel/idle.c
+++ b/arch/mips/kernel/idle.c
@@ -37,7 +37,6 @@ static void __cpuidle r3081_wait(void)
void __cpuidle r4k_wait(void)
{
- raw_local_irq_enable();
__r4k_wait();
raw_local_irq_disable();
}
--
2.48.1
next prev parent reply other threads:[~2025-03-15 19:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 19:40 [PATCH v6 0/1] MIPS: Fix idle VS timer enqueue Marco Crivellari
2025-03-15 19:40 ` Marco Crivellari [this message]
2025-03-19 11:07 ` [PATCH v6 1/1] " Thomas Bogendoerfer
2025-03-19 14:06 ` Frederic Weisbecker
2025-03-19 14:42 ` Thomas Bogendoerfer
2025-03-19 15:01 ` Frederic Weisbecker
2025-03-19 14:43 ` Frederic Weisbecker
2025-03-19 15:31 ` Thomas Bogendoerfer
2025-03-20 8:44 ` Marco Crivellari
2025-03-21 9:38 ` Thomas Bogendoerfer
2025-03-21 10:44 ` Marco Crivellari
2025-03-21 11:17 ` Thomas Bogendoerfer
2025-03-21 11:55 ` Maciej W. Rozycki
2025-03-21 11:53 ` Maciej W. Rozycki
2025-03-21 16:15 ` Marco Crivellari
2025-03-21 20:11 ` Maciej W. Rozycki
2025-03-25 14:08 ` Marco Crivellari
2025-03-26 1:20 ` Huacai Chen
2025-03-26 9:46 ` Marco Crivellari
2025-03-26 11:34 ` Thomas Bogendoerfer
2025-03-26 16:01 ` Maciej W. Rozycki
2025-03-28 10:42 ` Maciej W. Rozycki
2025-03-28 14:18 ` Maciej W. Rozycki
2025-03-31 10:11 ` Marco Crivellari
2025-03-31 20:09 ` Maciej W. Rozycki
2025-04-01 9:31 ` Jiaxun Yang
2025-04-02 11:42 ` Marco Crivellari
2025-04-03 12:00 ` Maciej W. Rozycki
2025-04-03 13:01 ` Marco Crivellari
2025-04-03 20:17 ` Maciej W. Rozycki
2025-04-04 3:18 ` Marco Crivellari
2025-03-21 21:09 ` Frederic Weisbecker
2025-03-22 16:08 ` Maciej W. Rozycki
2025-03-25 13:31 ` Frederic Weisbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250315194002.13778-2-marco.crivellari@suse.com \
--to=marco.crivellari@suse.com \
--cc=anna-maria@linutronix.de \
--cc=chenhuacai@kernel.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox