mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
	Witold Baryluk <baryluk@smp.if.uj.edu.pl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH] ftrace: Add internal recursive checks
Date: Wed, 25 May 2011 19:47:21 -0400	[thread overview]
Message-ID: <1306367241.1465.127.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1306366886.1465.124.camel@gandalf.stny.rr.com>

On Wed, 2011-05-25 at 19:41 -0400, Steven Rostedt wrote:
> On Thu, 2011-05-26 at 00:54 +0200, Thomas Gleixner wrote:
> > On Wed, 25 May 2011, Steven Rostedt wrote:

> > Errm, what means _MAY_? There are no users outside of kernel/trace/
> > for this right now. Are you saying that you forgot to update some code
> > or is this about random out of tree users?
> 
> Actually, I was thinking about perf, not some random out of tree user.
> But if this is needed, I hate to have to move the code then. It's not
> like it's modifying some internal to ftrace variable. It is modifying a
> variable in the task_struct. If there are other users that need it. Why
> not expose it in a core header? And it's not like ftrace.h is a bad
> location for this. ftrace.h is in fact made for function tracing.

Thinking about this a little more. I think I will put this in
kernel/trace/trace.h. Not for the reasons you give, but because the next
change in this area (for the next merge window) I want to have mcount do
the work, and then we only need one recursive bit set, and it will
handle function recursion by all users, and then we don't need to worry
about recursions due to the function tracer anymore :)

-- Steve



  reply	other threads:[~2011-05-25 23:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 18:27 Steven Rostedt
2011-05-25 18:57 ` Thomas Gleixner
2011-05-25 20:23   ` Steven Rostedt
2011-05-25 22:54     ` Thomas Gleixner
2011-05-25 23:41       ` Steven Rostedt
2011-05-25 23:47         ` Steven Rostedt [this message]
2011-05-27 12:48 ` [tip:perf/urgent] " tip-bot for Steven Rostedt

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=1306367241.1465.127.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=baryluk@smp.if.uj.edu.pl \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®