All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Pekka Paalanen <pq@iki.fi>
Cc: Ingo Molnar <mingo@elte.hu>, Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: ftrace and debugfs weird interaction
Date: Mon, 28 Apr 2008 16:34:11 -0400	[thread overview]
Message-ID: <20080428203411.GC27154@Krystal> (raw)
In-Reply-To: <20080428223535.4fe2aeca@daedalus.pq.iki.fi>

* Pekka Paalanen (pq@iki.fi) wrote:
> > * Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> > 
> > > Hi,
> > > 
> > > When trying to figure out what was going on with the sched tracer
> > > "tracing_enabled" file (sched-devel.git tree), I fell on this strange
> > > behavior :
> > > 
> > > echo 1>tracing_enabled seems _not_ to send 1 to the tracing_ctrl_write
> 
> Wait a minute, are you literally running the command:
> echo 1>tracing_enabled
> 
> If you are, you just echoed only a newline and directed stdout, stream 1,
> to the file. No? :-)
> 
> Could you try with a space:
> echo 1 > tracing_enabled
> 
> > > callback. However, sending garbage, e.g. echo s> tracing_enabled,
> > > correctly sends the 's' character down the chain. echo 0>tracing_enabled
> > > sometimes results in the callback not even being called.
> 
> Stream 0 is stdin, so... not sure what this would do. Probably nothing,
> just like you experienced.
> 

*duh*. Ok. That wasn't smart. You spotted the problem. Thanks a lot :)

Mathieu

> 
> Thanks.
> 
> -- 
> Pekka Paalanen
> http://www.iki.fi/pq/

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

      reply	other threads:[~2008-04-28 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26 18:54 ftrace and debugfs weird interaction Mathieu Desnoyers
2008-04-27  0:36 ` Greg KH
2008-04-28 15:39 ` Ingo Molnar
2008-04-28 19:27   ` Steven Rostedt
2008-04-28 19:35   ` Pekka Paalanen
2008-04-28 20:34     ` Mathieu Desnoyers [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=20080428203411.GC27154@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pq@iki.fi \
    --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 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.