public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Han Pingtian <phan@redhat.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] Fix disable set_ftrace_pid in ftrace_set_ftrace_pid.sh
Date: Tue, 22 Feb 2011 09:58:14 +0800	[thread overview]
Message-ID: <20110222015814.GA2883@hpt.nay.redhat.com> (raw)
In-Reply-To: <4D6217CB.1040506@cn.fujitsu.com>

On Mon, Feb 21, 2011 at 03:44:11PM +0800, Li Zefan wrote:
> Han Pingtian wrote:
> > It seems we need echo -1 to set_ftrace_pid to disable in. Or we'll get
> > these error message when running ftrace_stress:
> > 
> 
> kernel version?
2.6.32-114.0.1.el6.x86_64 , RHEL6.1.
> 
> This is the result from latest kernel:
> 
> # echo > set_ftrace_pid
> # echo -1 > set_ftrace_pid
> bash: echo: write error: Invalid argument
> 
Looks like latest kernel changed the behaviour. But the
Documentation/trace/ftrace.txt hasn't been updated:

     yum-updatesd-3111  [003]  1637.254683: lock_hrtimer_base <-hrtimer_try_to_cancel
     yum-updatesd-3111  [003]  1637.254685: fget_light <-do_sys_poll
     yum-updatesd-3111  [003]  1637.254686: pipe_poll <-do_sys_poll
# echo -1 > set_ftrace_pid
# cat trace |head
 # tracer: function
 #
 #           TASK-PID    CPU#    TIMESTAMP  FUNCTION
 

Thanks.
> > ...
> > ftrace_stress_test/ftrace_stress/ftrace_set_ftrace_pid.sh: line 39: echo: write error: Invalid argument
> > ...
> > ---
> >  .../ftrace_stress/ftrace_set_ftrace_pid.sh         |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/testcases/kernel/tracing/ftrace_stress_test/ftrace_stress/ftrace_set_ftrace_pid.sh b/testcases/kernel/tracing/ftrace_stress_test/ftrace_stress/ftrace_set_ftrace_pid.sh
> > index 541215c..bd08f04 100755
> > --- a/testcases/kernel/tracing/ftrace_stress_test/ftrace_stress/ftrace_set_ftrace_pid.sh
> > +++ b/testcases/kernel/tracing/ftrace_stress_test/ftrace_stress/ftrace_set_ftrace_pid.sh
> > @@ -36,7 +36,7 @@ for ((; ; ))
> >  			eval echo $str >> "$TRACING_PATH"/set_ftrace_pid
> >  		}
> >  
> > -		echo > "$TRACING_PATH"/set_ftrace_pid
> > +		echo -1 > "$TRACING_PATH"/set_ftrace_pid
> >  	}
> >  
> >  	sleep 1

-- 
Han Pingtian
Quality Engineer
hpt @ #kernel-qe
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY

------------------------------------------------------------------------------
Index, Search & Analyze Logs and other IT data in Real-Time with Splunk 
Collect, index and harness all the fast moving IT data generated by your 
applications, servers and devices whether physical, virtual or in the cloud.
Deliver compliance at lower cost and gain new business insights. 
Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2011-02-22  1:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10  7:23 [LTP] [PATCH] Fix disable set_ftrace_pid in ftrace_set_ftrace_pid.sh Han Pingtian
2011-02-21  7:37 ` Han Pingtian
2011-02-21  7:44 ` Li Zefan
2011-02-22  1:58   ` Han Pingtian [this message]
2011-02-22  2:08     ` Li Zefan
2011-02-22  3:55       ` Han Pingtian

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=20110222015814.GA2883@hpt.nay.redhat.com \
    --to=phan@redhat.com \
    --cc=lizf@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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