public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
	laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
	josht@linux.vnet.ibm.com, dvhltc@us.ibm.com, niv@us.ibm.com,
	tglx@linutronix.de, peterz@infradead.org
Subject: Re: [PATCH -tip 1/2] Add "notrace" to RCU function headers used by ftrace.
Date: Mon, 24 Aug 2009 19:02:21 -0700	[thread overview]
Message-ID: <20090825020221.GA7355@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0908241938330.6710@gandalf.stny.rr.com>

On Mon, Aug 24, 2009 at 07:38:51PM -0400, Steven Rostedt wrote:
> 
> On Mon, 24 Aug 2009, Paul E. McKenney wrote:
> 
> > Both rcu_read_lock_sched_notrace() and rcu_read_unlock_sched_notrace()
> > are used by ftrace, and thus need to be marked "notrace".  Unfortunately,
> > my naive assumption that gcc would see the inner "notrace" does not hold.
> > Kudos to Lai Jiangshan for noting this.
> > 
> > Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > ---
> >  include/linux/rcupdate.h |    4 ++--
> >  1 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h
> > index ec90fc3..8b4422c 100644
> > --- a/include/linux/rcupdate.h
> > +++ b/include/linux/rcupdate.h
> > @@ -191,7 +191,7 @@ static inline void rcu_read_lock_sched(void)
> >  	__acquire(RCU_SCHED);
> >  	rcu_read_acquire();
> >  }
> > -static inline void rcu_read_lock_sched_notrace(void)
> > +static inline notrace void rcu_read_lock_sched_notrace(void)
> >  {
> >  	preempt_disable_notrace();
> >  	__acquire(RCU_SCHED);
> > @@ -209,7 +209,7 @@ static inline void rcu_read_unlock_sched(void)
> >  	__release(RCU_SCHED);
> >  	preempt_enable();
> >  }
> > -static inline void rcu_read_unlock_sched_notrace(void)
> > +static inline notrace void rcu_read_unlock_sched_notrace(void)
> 
> Funny, inlines should not be traced. Is gcc ignoring the inlines here?

Well, that was my line of thinking as well, until Lai Jiangshan set
me straight.  Version 4.x of gcc apparently decides on a case-by-case
basis.

							Thanx, Paul

  parent reply	other threads:[~2009-08-25  2:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 16:41 [PATCH -tip 0/2] Temporary RCU fixes for notrace and hotplug CPU Paul E. McKenney
2009-08-24 16:42 ` [PATCH -tip 1/2] Add "notrace" to RCU function headers used by ftrace Paul E. McKenney
2009-08-24 23:38   ` Steven Rostedt
2009-08-25  0:10     ` Mathieu Desnoyers
2009-08-25  2:02     ` Paul E. McKenney [this message]
2009-08-25  2:11       ` Steven Rostedt
2009-08-25  2:25         ` Paul E. McKenney
2009-08-25  7:13   ` [tip:core/rcu] rcu: " tip-bot for Paul E. McKenney
2009-08-24 16:42 ` [PATCH -tip 2/2] Add CPU-offline processing for single-node configurations Paul E. McKenney
2009-08-25  7:13   ` [tip:core/rcu] rcu: " tip-bot for Paul E. McKenney
2009-08-25  6:55 ` [PATCH -tip 0/2] Temporary RCU fixes for notrace and hotplug CPU Ingo Molnar
2009-08-25  8:00   ` Ingo Molnar
2009-08-25 16:12     ` Paul E. McKenney
2009-08-25 16:25       ` Mathieu Desnoyers
2009-08-25 17:11         ` Paul E. McKenney
2009-08-25 18:02           ` Mathieu Desnoyers
2009-08-25 18:36             ` [PATCH -tip] " Paul E. McKenney
2009-08-26  0:53               ` Lai Jiangshan
2009-08-26  1:31                 ` Paul E. McKenney
2009-08-25 15:40   ` Paul E. McKenney
2009-08-25 18:19     ` Ingo Molnar
2009-08-25 18:41       ` Paul E. McKenney
2009-08-25 18:21     ` [tip:core/rcu] rcu: Add #ifdef to suppress __rcu_offline_cpu() warning in !HOTPLUG_CPU builds tip-bot for Paul E. McKenney

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=20090825020221.GA7355@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dipankar@in.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=josht@linux.vnet.ibm.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=niv@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox