From: Li Zefan <lizf@cn.fujitsu.com>
To: jolsa@redhat.com
Cc: mingo@elte.hu, rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing - support multiple pids in set_pid_ftrace file
Date: Tue, 15 Sep 2009 17:40:07 +0800 [thread overview]
Message-ID: <4AAF60F7.6040107@cn.fujitsu.com> (raw)
In-Reply-To: <1253005169-32709-1-git-send-email-jolsa@redhat.com>
jolsa@redhat.com wrote:
> Adding the possibility to set more than 1 pid in the set_pid_ftrace file,
> thus allowing to trace more than 1 independent processes.
>
> Usage:
>
> sh-4.0# echo 284 > ./set_ftrace_pid
> sh-4.0# cat ./set_ftrace_pid
> 284
> sh-4.0# echo 1 >> ./set_ftrace_pid
> sh-4.0# echo 0 >> ./set_ftrace_pid
> sh-4.0# cat ./set_ftrace_pid
> swapper tasks
> 1
> 284
> sh-4.0# echo 4 > ./set_ftrace_pid
> sh-4.0# cat ./set_ftrace_pid
> 4
> sh-4.0# echo > ./set_ftrace_pid
> sh-4.0# cat ./set_ftrace_pid
> no pid
> sh-4.0#
>
>
> wbr,
> jirka
>
> Signed-off-by: Jiri Olsa <jolsa@redhat.com>
> ---
> kernel/trace/ftrace.c | 226 +++++++++++++++++++++++++++++++++++--------------
> kernel/trace/trace.h | 4 +-
> 2 files changed, 164 insertions(+), 66 deletions(-)
>
...
> +static void ftrace_pid_reset(void)
> +{
> + struct ftrace_pid *fpid, *safe;
> +
> + mutex_lock(&ftrace_lock);
> + list_for_each_entry_safe(fpid, safe, &ftrace_pids, list) {
> + struct pid *pid = fpid->pid;
> +
> + clear_ftrace_pid_task(&pid);
Now we can change clear_ftrace_pid_task() to take struct pid *
instead of struct pid**.
> +
> + if (pid != ftrace_swapper_pid)
> + put_pid(pid);
> +
clear_ftrace_pid_task() already called put_pid().
> + list_del(&fpid->list);
> + kfree(fpid);
> + }
> +
> + ftrace_update_pid_func();
> + ftrace_startup_enable(0);
> +
> + mutex_unlock(&ftrace_lock);
> +}
> +
...
> static ssize_t
> ftrace_pid_write(struct file *filp, const char __user *ubuf,
> size_t cnt, loff_t *ppos)
> {
> - struct pid *pid;
> char buf[64];
> long val;
> int ret;
> @@ -2897,57 +3016,36 @@ ftrace_pid_write(struct file *filp, const char __user *ubuf,
>
> buf[cnt] = 0;
>
> + /*
> + * Allow the "echo > set_ftrace_pid" to clean
> + * the pids quietly.
> + */
> + if (!*ppos && *buf == '\n' && cnt == 1)
> + return 1;
> +
How about:
strstrip(buf);
if (strlen(buf) == 0)
return 1;
So "echo -n '' > set_ftrace_pid" works too.
> ret = strict_strtol(buf, 10, &val);
> if (ret < 0)
> return ret;
>
next prev parent reply other threads:[~2009-09-15 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 8:59 [PATCH] tracing - support multiple pids in set_pid_ftrace file jolsa
2009-09-15 9:40 ` Li Zefan [this message]
2009-09-15 12:36 ` Jiri Olsa
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=4AAF60F7.6040107@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=jolsa@redhat.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