From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: rostedt@goodmis.org, mingo@elte.hu, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] ftrace: Add debug_print trace to print data from kernel to userspace
Date: Sun, 16 Nov 2008 16:19:04 +0530 [thread overview]
Message-ID: <20081116104904.GB25788@skywalker> (raw)
In-Reply-To: <c62985530811140639k1004a8f9k968c3e0949d1a309@mail.gmail.com>
On Fri, Nov 14, 2008 at 03:39:29PM +0100, Frédéric Weisbecker wrote:
> 2008/11/14 Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>:
> > We also want to make sure dp_printk doesn't do anything when tracer
> > is disabled. We do
> >
> > int do_dp_printk(const char *fmt, ...)
> > {
> > int ret;
> > va_list args;
> >
> > if (!tracer_enabled)
> > return 0;
>
>
> In this case you just have to do
> echo 0 > /debug/tracing/tracing_enabled
> And the entries will not be printed anymore....
That would prevent us to have both dp_printk and debug_dump
used at the same time. Both will them depend on the tracer_enabled
flag. That means the output of these call will also interact with
rest of the tracer output.
-aneesh
next prev parent reply other threads:[~2008-11-16 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 10:46 [PATCH 1/3] ftrace: add proper bin iterator support Aneesh Kumar K.V
2008-11-14 10:46 ` [PATCH 2/3] ftrace: Add debug_print trace to print data from kernel to userspace Aneesh Kumar K.V
2008-11-14 10:46 ` [PATCH 3/3] ftrace: Add debug_dump trace to dump binary " Aneesh Kumar K.V
2008-11-14 11:54 ` Frédéric Weisbecker
2008-11-14 13:19 ` Frédéric Weisbecker
2008-11-14 13:25 ` Frédéric Weisbecker
2008-11-14 11:21 ` [PATCH 2/3] ftrace: Add debug_print trace to print " Frédéric Weisbecker
2008-11-14 13:46 ` Aneesh Kumar K.V
2008-11-14 14:39 ` Frédéric Weisbecker
2008-11-16 10:49 ` Aneesh Kumar K.V [this message]
2008-11-14 11:25 ` Frédéric Weisbecker
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=20081116104904.GB25788@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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®