From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: [PATCH 5/5] perf: Make perf aware of tracefs
Date: Sun, 25 Jan 2015 22:50:10 +0900 [thread overview]
Message-ID: <20150125135010.GA24454@danjae> (raw)
In-Reply-To: <20150124181449.157590751@goodmis.org>
Hi Steve,
On Sat, Jan 24, 2015 at 01:13:35PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
>
> As tracefs may be mounted instead of debugfs to get to the event directories,
> have perf know about tracefs, and use that file system over debugfs if it
> is present.
>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> ---
> const char *find_tracing_dir(void)
> {
> + const char *tracing_dir = "";
> static char *tracing;
> static int tracing_found;
> const char *debugfs;
> @@ -351,11 +385,15 @@ const char *find_tracing_dir(void)
> if (tracing_found)
> return tracing;
>
> - debugfs = find_debugfs();
> - if (!debugfs)
> - return NULL;
> + debugfs = find_tracefs();
> + if (!debugfs) {
> + tracing_dir = "/tracing";
> + debugfs = find_debugfs();
> + if (!debugfs)
> + return NULL;
> + }
>
> - if (asprintf(&tracing, "%s/tracing", debugfs) < 0)
> + if (asprintf(&tracing, "%s%s", tracing_dir, debugfs) < 0)
s/tracing_dir, debugfs/debugfs, tracing_dir/
Thanks,
Namhyung
> return NULL;
>
> tracing_found = 1;
> diff --git a/tools/perf/util/util.h b/tools/perf/util/util.h
> index 027a5153495c..73c2f8e557ab 100644
> --- a/tools/perf/util/util.h
> +++ b/tools/perf/util/util.h
> @@ -75,6 +75,7 @@
> #include <linux/types.h>
> #include <sys/ttydefaults.h>
> #include <api/fs/debugfs.h>
> +#include <api/fs/tracefs.h>
> #include <termios.h>
> #include <linux/bitops.h>
> #include <termios.h>
> --
> 2.1.4
>
>
next prev parent reply other threads:[~2015-01-25 13:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 18:13 [PATCH 0/5] perf: Have perf become tracefs aware Steven Rostedt
2015-01-24 18:13 ` [PATCH 1/5] tools lib fs: Add helper to find mounted file systems Steven Rostedt
2015-01-25 16:41 ` Jiri Olsa
2015-01-25 19:20 ` Steven Rostedt
2015-01-24 18:13 ` [PATCH 2/5] tools lib api fs: Add tracefs mount helper functions Steven Rostedt
2015-01-25 16:45 ` Jiri Olsa
2015-01-25 19:22 ` Steven Rostedt
2015-01-25 16:51 ` Jiri Olsa
2015-01-25 19:24 ` Steven Rostedt
2015-01-25 16:56 ` Jiri Olsa
2015-01-25 19:26 ` Steven Rostedt
2015-01-26 9:02 ` Jiri Olsa
2015-01-26 14:26 ` Steven Rostedt
2015-01-26 14:31 ` Jiri Olsa
2015-01-26 14:44 ` Arnaldo Carvalho de Melo
2015-01-24 18:13 ` [PATCH 3/5] tools lib api fs: Add DEBUGFS_DEFAULT_PATH macro Steven Rostedt
2015-01-24 18:13 ` [PATCH 4/5] tools lib api fs: Add {tracefs,debugfs}_configured() functions Steven Rostedt
2015-01-25 17:02 ` Jiri Olsa
2015-01-25 19:27 ` Steven Rostedt
2015-01-24 18:13 ` [PATCH 5/5] perf: Make perf aware of tracefs Steven Rostedt
2015-01-25 13:50 ` Namhyung Kim [this message]
2015-01-25 19:19 ` Steven Rostedt
2015-01-25 17:34 ` Jiri Olsa
2015-01-25 19:31 ` Steven Rostedt
2015-01-26 8:57 ` 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=20150125135010.GA24454@danjae \
--to=namhyung@kernel.org \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--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.