From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Olsa <jolsa@redhat.com>
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>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH 6/6 v2] perf: Make perf aware of tracefs
Date: Tue, 3 Feb 2015 11:45:50 -0500 [thread overview]
Message-ID: <20150203114550.6646db20@gandalf.local.home> (raw)
In-Reply-To: <20150203141625.GA1359@krava.brq.redhat.com>
On Tue, 3 Feb 2015 15:16:25 +0100
Jiri Olsa <jolsa@redhat.com> wrote:
> On Mon, Feb 02, 2015 at 02:35:07PM -0500, Steven Rostedt wrote:
>
> SNIP
>
> > }
> > @@ -325,12 +351,19 @@ const char *perf_debugfs_mount(const char *mountpoint)
> > void perf_debugfs_set_path(const char *mntpt)
> > {
> > snprintf(debugfs_mountpoint, strlen(debugfs_mountpoint), "%s", mntpt);
> > - set_tracing_events_path(mntpt);
> > + set_tracing_events_path("tracing/", mntpt);
> > +}
> > +
> > +static const char *find_tracefs(void)
> > +{
> > + const char *path = __perf_tracefs_mount(NULL);
> > +
> > + return path;
>
> I guess you ommited the fprint(stderr... ) warning on purpose
> (like in find_debugfs), because the tracefs is not upstream yet, right?
Right, because I didn't want people complaining about using a new perf
with an old kernel, and suddenly get warnings.
>
> maybe we want at least pr_debug warning here..
> anyway, other than that the patchset looks ok to me:
I was thinking that we could add one later, when tracefs is more common.
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
Thanks!
Arnaldo, do you want to pick this up?
-- Steve
next prev parent reply other threads:[~2015-02-03 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 19:35 [PATCH 0/6 v2] perf: Have perf become tracefs aware Steven Rostedt
2015-02-02 19:35 ` [PATCH 1/6 v2] perf: Do not check debugfs MAGIC for tracing files Steven Rostedt
2015-02-18 18:27 ` [tip:perf/core] perf tools: " tip-bot for Steven Rostedt (Red Hat)
2015-02-02 19:35 ` [PATCH 2/6 v2] tools lib fs: Add helper to find mounted file systems Steven Rostedt
2015-02-18 18:28 ` [tip:perf/core] " tip-bot for Steven Rostedt (Red Hat)
2015-02-02 19:35 ` [PATCH 3/6 v2] tools lib api fs: Add tracefs mount helper functions Steven Rostedt
2015-02-18 18:28 ` [tip:perf/core] " tip-bot for Steven Rostedt (Red Hat)
2015-02-02 19:35 ` [PATCH 4/6 v2] tools lib api fs: Add DEBUGFS_DEFAULT_PATH macro Steven Rostedt
2015-02-18 18:28 ` [tip:perf/core] tools lib api debugfs: " tip-bot for Steven Rostedt (Red Hat)
2015-02-02 19:35 ` [PATCH 5/6 v2] tools lib api fs: Add {tracefs,debugfs}_configured() functions Steven Rostedt
2015-02-18 18:29 ` [tip:perf/core] tools lib api fs: Add {tracefs, debugfs}_configured() functions tip-bot for Steven Rostedt (Red Hat)
2015-02-02 19:35 ` [PATCH 6/6 v2] perf: Make perf aware of tracefs Steven Rostedt
2015-02-03 14:16 ` Jiri Olsa
2015-02-03 16:45 ` Steven Rostedt [this message]
2015-02-06 8:35 ` Arnaldo Carvalho de Melo
2015-02-08 14:12 ` Namhyung Kim
2015-02-09 15:24 ` Steven Rostedt
2015-02-18 18:29 ` [tip:perf/core] perf tools: " tip-bot for Steven Rostedt (Red Hat)
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=20150203114550.6646db20@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.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;
as well as URLs for NNTP newsgroup(s).