From: Frederic Weisbecker <frederic@kernel.org>
To: "bibo, mao" <maobibo@loongson.cn>
Cc: Peter Zijlstra <peterz@infradead.org>,
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: Mon, 24 Apr 2023 10:26:58 +0200 [thread overview]
Message-ID: <ZEY9UvvuTXYx3QEA@lothringen> (raw)
In-Reply-To: <7d91fa2a-57c5-6c78-8e2d-7fbdd6a11cba@loongson.cn>
On Sun, Apr 23, 2023 at 09:52:49PM +0800, bibo, mao wrote:
>
>
> 在 2023/4/22 23:04, Peter Zijlstra 写道:
> > On Sat, Apr 22, 2023 at 04:21:45PM +0200, Frederic Weisbecker wrote:
> > > 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 do not know much details about scheduler and timer, if the interrupt
> happens between the call, will flag _TIF_NEED_RESCHED be set? If it is set,
> the rollback will still apply.
Nop, TIF_NEED_RESCHED is set only if a task is ready to run after the interrupt,
not if the interrupt only modified/added a timer.
> > @@ -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
> It is more reasonable with this patch, this will jump out of idle function
> directly after interrupt returns. If so, can we remove checking
> _TIF_NEED_RESCHED in idle ASM function?
Indeed we can remove the check to TIF_RESCHED!
Thanks!
next prev parent reply other threads:[~2023-04-24 8:27 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
2023-04-22 15:04 ` Peter Zijlstra
2023-04-23 13:52 ` bibo, mao
2023-04-24 8:26 ` Frederic Weisbecker [this message]
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=ZEY9UvvuTXYx3QEA@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=maobibo@loongson.cn \
--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.