[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230815223926.GC971582@hirez.programming.kicks-ass.net>
Date: Wed, 16 Aug 2023 00:39:26 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Phil Auld <pauld@...hat.com>
Cc: bigeasy@...utronix.de, tglx@...utronix.de,
linux-kernel@...r.kernel.org, bsegall@...gle.com,
boqun.feng@...il.com, swood@...hat.com, bristot@...hat.com,
dietmar.eggemann@....com, mingo@...hat.com, jstultz@...gle.com,
juri.lelli@...hat.com, mgorman@...e.de, rostedt@...dmis.org,
vschneid@...hat.com, vincent.guittot@...aro.org,
longman@...hat.com, will@...nel.org
Subject: Re: [PATCH 3/6] sched: Extract __schedule_loop()
On Tue, Aug 15, 2023 at 06:33:01PM -0400, Phil Auld wrote:
> Hi Peter,
>
> On Tue, Aug 15, 2023 at 01:01:24PM +0200 Peter Zijlstra wrote:
> > From: Thomas Gleixner <tglx@...utronix.de>
> >
> > There are currently two implementations of this basic __schedule()
> > loop, and there is soon to be a third.
> >
> > Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
> > Link: https://lkml.kernel.org/r/20230427111937.2745231-2-bigeasy@linutronix.de
> > ---
> > kernel/sched/core.c | 21 +++++++++++----------
> > 1 file changed, 11 insertions(+), 10 deletions(-)
> >
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -6787,16 +6787,21 @@ static void sched_update_worker(struct t
> > }
> > }
> >
> > -asmlinkage __visible void __sched schedule(void)
> > +static __always_inline void __schedule_loop(unsigned int sched_mode)
>
> I think this needs __sched or it's the only thing that ever shows up
> in wchan. E.g.
>
> 16995 0 bash S __schedule_loop.constprop.0
> 17036 1 kworker/ I __schedule_loop.constprop.0
> 17151 1 kworker/ I __schedule_loop.constprop.0
> 17235 0 sleep S __schedule_loop.constprop.0
> 17236 4 ps R -
But but but __always_inline... ?!?
Powered by blists - more mailing lists