From: Frederic Weisbecker <frederic@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Loongson (and other $ARCHs?) idle VS timer enqueue
Date: Sat, 22 Apr 2023 16:21:45 +0200 [thread overview]
Message-ID: <ZEPteS82TbIhMQxe@lothringen> (raw)
In-Reply-To: <20230422081700.GB1214746@hirez.programming.kicks-ass.net>
On Sat, Apr 22, 2023 at 10:17:00AM +0200, Peter Zijlstra wrote:
> diff --git a/arch/loongarch/kernel/genex.S b/arch/loongarch/kernel/genex.S
> index 44ff1ff64260..5a102ff80de0 100644
> --- a/arch/loongarch/kernel/genex.S
> +++ b/arch/loongarch/kernel/genex.S
> @@ -40,6 +40,7 @@ SYM_FUNC_START(handle_vint)
> ori t0, t0, 0x1f
> xori t0, t0, 0x1f
> bne t0, t1, 1f
> + addi.d t0, t0, 0x20
> LONG_S t0, sp, PT_ERA
> 1: move a0, sp
> move a1, sp
But the interrupts are enabled in C from arch_cpu_idle(), which
only then calls the ASM __arch_cpu_idle(). So if the interrupt happens
somewhere in between the call, the rollback (or fast-forward now)
doesn't apply.
I guess interrupts need to be re-enabled from ASM in the beginning
of __arch_cpu_idle() so that it's part of the fast-forward region.
> diff --git a/arch/mips/kernel/genex.S b/arch/mips/kernel/genex.S
> index b6de8e88c1bd..cd6aae441ad9 100644
> --- a/arch/mips/kernel/genex.S
> +++ b/arch/mips/kernel/genex.S
> @@ -140,6 +140,7 @@ LEAF(__r4k_wait)
> ori k0, 0x1f /* 32 byte rollback region */
> xori k0, 0x1f
> bne k0, k1, \handler
> + addiu k0, 0x20
> MTC0 k0, CP0_EPC
> .set pop
> .endm
The same seem to apply with interrupts being re-enabled by r4k_wait().
Thanks.
next prev parent reply other threads:[~2023-04-22 14:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 12:36 Loongson (and other $ARCHs?) idle VS timer enqueue Frederic Weisbecker
2023-04-21 14:24 ` Peter Zijlstra
2023-04-21 16:47 ` Frederic Weisbecker
2023-04-22 8:08 ` Peter Zijlstra
2023-04-22 11:38 ` Peter Zijlstra
2023-04-22 14:48 ` Frederic Weisbecker
2023-04-21 15:24 ` Thomas Gleixner
2023-04-21 16:55 ` Frederic Weisbecker
2023-04-21 20:28 ` Thomas Gleixner
2023-04-22 8:17 ` Peter Zijlstra
2023-04-22 8:22 ` Peter Zijlstra
2023-04-22 14:21 ` Frederic Weisbecker [this message]
2023-04-22 15:04 ` Peter Zijlstra
2023-04-23 13:52 ` bibo, mao
2023-04-24 8:26 ` Frederic Weisbecker
2023-04-24 11:23 ` maobibo
2023-04-25 11:49 ` Peter Zijlstra
2023-04-25 13:25 ` maobibo
2023-04-25 13:28 ` WANG Xuerui
2023-04-26 0:46 ` maobibo
2023-04-26 2:10 ` WANG Xuerui
2023-04-26 2:23 ` maobibo
2023-06-06 22:07 ` 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=ZEPteS82TbIhMQxe@lothringen \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.