From: Masami Hiramatsu <mhiramat@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [resend][PATCH 1/2] kprobetrace,doc: shell need single quote to use $ character
Date: Thu, 14 Jan 2010 00:00:35 -0500 [thread overview]
Message-ID: <4B4EA4F3.6090401@redhat.com> (raw)
In-Reply-To: <20100114111032.D720.A69D9226@jp.fujitsu.com>
KOSAKI Motohiro wrote:
> shell interpret $val is as shell variable. thus we need quote if
> we use echo command.
>
> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> Acked-by: Masami Hiramatsu <mhiramat@redhat.com>
Hi Ingo and KOSAKI-san,
Sorry, now this patch conflicts with my patch(commit 1464010) on the
latest -tip tree. The patch drops $argN support, so I updated the
1st example command.
Thank you,
> ---
> Documentation/trace/kprobetrace.txt | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/trace/kprobetrace.txt b/Documentation/trace/kprobetrace.txt
> index 47aabee..2be6e19 100644
> --- a/Documentation/trace/kprobetrace.txt
> +++ b/Documentation/trace/kprobetrace.txt
> @@ -82,13 +82,13 @@ Usage examples
> To add a probe as a new event, write a new definition to kprobe_events
> as below.
>
> - echo p:myprobe do_sys_open dfd=$arg0 filename=$arg1 flags=$arg2 mode=$arg3 > /sys/kernel/debug/tracing/kprobe_events
> + echo 'p:myprobe do_sys_open dfd=$arg0 filename=$arg1 flags=$arg2 mode=$arg3' > /sys/kernel/debug/tracing/kprobe_events
>
> This sets a kprobe on the top of do_sys_open() function with recording
> 1st to 4th arguments as "myprobe" event. As this example shows, users can
> choose more familiar names for each arguments.
>
> - echo r:myretprobe do_sys_open $retval >> /sys/kernel/debug/tracing/kprobe_events
> + echo 'r:myretprobe do_sys_open $retval' >> /sys/kernel/debug/tracing/kprobe_events
>
> This sets a kretprobe on the return point of do_sys_open() function with
> recording return value as "myretprobe" event.
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2010-01-14 4:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 2:14 [resend][PATCH 1/2] kprobetrace,doc: shell need single quote to use $ character KOSAKI Motohiro
2010-01-14 2:16 ` [resend][PATCH 2/2] kprobetrace, doc: Add the explanation to remove probe points KOSAKI Motohiro
2010-01-14 5:00 ` Masami Hiramatsu [this message]
2010-01-14 5:17 ` [resend][PATCH 1/2] kprobetrace,doc: shell need single quote to use $ character KOSAKI Motohiro
2010-01-17 7:14 ` Ingo Molnar
2010-01-19 2:35 ` [PATCH -tip 1/2] kprobetrace, doc: " Masami Hiramatsu
2010-01-20 7:12 ` [tip:perf/core] kprobetrace, doc: Shell needs " tip-bot for Motohiro KOSAKI
2010-01-19 2:35 ` [PATCH -tip 2/2] kprobetrace, doc: Add the explanation to remove probe points Masami Hiramatsu
2010-01-19 2:45 ` Li Zefan
2010-01-19 3:05 ` Masami Hiramatsu
2010-01-19 3:05 ` Li Zefan
2010-01-19 4:22 ` Masami Hiramatsu
2010-01-20 6:18 ` Ingo Molnar
2010-01-20 7:12 ` [tip:perf/core] " tip-bot for Motohiro KOSAKI
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=4B4EA4F3.6090401@redhat.com \
--to=mhiramat@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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