All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Hillf Danton <hillf.zj@alibaba-inc.com>
Cc: 'Sebastian Andrzej Siewior' <bigeasy@linutronix.de>,
	'Thomas Gleixner' <tglx@linutronix.de>,
	'LKML' <linux-kernel@vger.kernel.org>,
	'linux-rt-users' <linux-rt-users@vger.kernel.org>
Subject: Re: [patch]  sched,rt: __always_inline preemptible_lazy()
Date: Mon, 22 Feb 2016 05:03:05 +0100	[thread overview]
Message-ID: <1456113785.3706.5.camel@gmail.com> (raw)
In-Reply-To: <00a501d16d22$30045140$900cf3c0$@alibaba-inc.com>

On Mon, 2016-02-22 at 11:36 +0800, Hillf Danton wrote:
> > 
> > homer: # nm kernel/sched/core.o|grep preemptible_lazy
> > 00000000000000b5 t preemptible_lazy
> > 
> > echo wakeup_rt > current_tracer ==> Welcome to infinity.
> > 
> > Signed-off-bx: Mike Galbraith <umgwanakikbuti@gmail.com>
> > ---
> 
> Fat finger?

Yeah, my fingers don't take direction all that well.

> BTW, would you please make a better description of the
> problem this patch is trying to address/fix?

Ok, I thought it was clear what happens.

sched,rt: __always_inline preemptible_lazy()

Functions called within a notrace function must either also be
notrace or be inlined, lest recursion blow the stack.

homer: # nm kernel/sched/core.o|grep preemptible_lazy
00000000000000b5 t preemptible_lazy

echo wakeup_rt > current_tracer ==> Welcome to infinity.

Signed-off-by: Mike Galbraith <umgwanakikbuti@gmail.com>
---
 kernel/sched/core.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -3469,7 +3469,7 @@ static void __sched notrace preempt_sche
  * set by a RT task. Oterwise we try to avoid beeing scheduled out as long as
  * preempt_lazy_count counter >0.
  */
-static int preemptible_lazy(void)
+static __always_inline int preemptible_lazy(void)
 {
 	if (test_thread_flag(TIF_NEED_RESCHED))
 		return 1;

  reply	other threads:[~2016-02-22  4:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22  3:36 [patch] sched,rt: __always_inline preemptible_lazy() Hillf Danton
2016-02-22  4:03 ` Mike Galbraith [this message]
2016-02-22  5:16   ` Hillf Danton
2016-02-26 10:17   ` Sebastian Andrzej Siewior
  -- strict thread matches above, loose matches on Subject: below --
2016-01-18  9:08 [rfc patch v4.4-rt2] sched: fix up preempt lazy forward port Mike Galbraith
2016-01-18 20:18 ` Sebastian Andrzej Siewior
2016-01-19  2:29   ` Mike Galbraith
2016-01-21 12:54     ` Sebastian Andrzej Siewior
2016-02-21 15:11       ` [patch] sched,rt: __always_inline preemptible_lazy() Mike Galbraith

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=1456113785.3706.5.camel@gmail.com \
    --to=umgwanakikbuti@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=hillf.zj@alibaba-inc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --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.