LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Zdenek Kabelac <zdenek.kabelac@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: sys_sched_yield keeps locked irq before call of schedule()
Date: Thu, 6 Nov 2008 09:46:57 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.1.10.0811060942300.31011@gandalf.stny.rr.com> (raw)
In-Reply-To: <20081106143428.GE13023@elte.hu>
On Thu, 6 Nov 2008, Ingo Molnar wrote:
> >
> > Quick note. Currently ftrace_printk only shows up if it is set in the
> > iter_ctrl.
> >
> > echo trace_printk > /debug/tracing/iter_ctrl
> >
> > I'll send out a patch to have it on by default.
>
> ok, agreed - but in that case please make the NOP tracer
> tracing_enabled=0 by default. (we'll get a lot of ftrace_printk
> tracepoints by default otherwise)
Hmm, I think it may be good to leave it on even for the nop tracer.
ftrace_printk's should not be out in open code unless someone is actually
debugging it. You can use ftrace_printk inside a tracer to write stuff,
but that printk should be protected somehow by the encompassing tracer.
i.e.
some_tracer(void) {
if (!tracer_enabled)
return;
ftrace_printk("my special stuff\n");
}
I would think if someone is debugging their code by using ftrace_printk,
they probably want it to show up right away, without having to remember to
do a...
echo trace_printk > /debug/tracing/iter_ctrl
And still have it show up in the nop tracer.
-- Steve
prev parent reply other threads:[~2008-11-06 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 12:57 Zdenek Kabelac
2008-11-05 13:01 ` Ingo Molnar
2008-11-05 13:09 ` Zdenek Kabelac
2008-11-05 14:05 ` Arnd Bergmann
2008-11-05 14:37 ` Zdenek Kabelac
2008-11-06 7:57 ` Ingo Molnar
2008-11-06 13:46 ` Steven Rostedt
2008-11-06 14:34 ` Ingo Molnar
2008-11-06 14:46 ` Steven Rostedt [this message]
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=alpine.DEB.1.10.0811060942300.31011@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zdenek.kabelac@gmail.com \
--subject='Re: sys_sched_yield keeps locked irq before call of schedule()' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).