linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: duchangbin <changbin.du@huawei.com>
To: James Clark <james.clark@linaro.org>
Cc: duchangbin <changbin.du@huawei.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	"Arnaldo Carvalho de Melo" <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH] perf ftrace: Detect whether ftrace is enabled on system
Date: Wed, 11 Sep 2024 10:00:31 +0000	[thread overview]
Message-ID: <526bf9fecede4effa859214683201518@huawei.com> (raw)
In-Reply-To: <4fa0229e-630b-4b6e-8882-3d8a5793a9dd@linaro.org>

On Wed, Sep 11, 2024 at 10:45:16AM +0100, James Clark wrote:
> 
> 
> On 10/09/2024 04:36, Changbin Du wrote:
> > To make error messages more accurate, this change detects whether ftrace is
> > enabled on system by checking trace file "set_ftrace_pid".
> > 
> > Before:
> > ~ # perf ftrace
> > failed to reset ftrace
> > 
> > After:
> > ~ # perf ftrace
> > ftrace is not supported on this system
> > 
> > Signed-off-by: Changbin Du <changbin.du@huawei.com>
> > ---
> >   tools/perf/builtin-ftrace.c | 24 ++++++++++++++++++++++++
> >   1 file changed, 24 insertions(+)
> > 
> > diff --git a/tools/perf/builtin-ftrace.c b/tools/perf/builtin-ftrace.c
> > index eb30c8eca488..e1dc2768bc0f 100644
> > --- a/tools/perf/builtin-ftrace.c
> > +++ b/tools/perf/builtin-ftrace.c
> > @@ -1112,6 +1112,24 @@ static int parse_graph_tracer_opts(const struct option *opt,
> >   	return 0;
> >   }
> > +static bool is_ftrace_supported(void)
> > +{
> > +	char *file;
> > +	bool supported = false;
> > +
> > +	file = get_tracing_file("set_ftrace_pid");
> > +	if (!file) {
> > +		pr_debug("cannot get tracing file set_ftrace_pid\n");
> > +		return false;
> > +	}
> > +
> > +	if (!access(file, F_OK))
> > +		supported = true;
> > +
> > +	put_tracing_file(file);
> > +	return supported;
> > +}
> > +
> >   enum perf_ftrace_subcommand {
> >   	PERF_FTRACE_NONE,
> >   	PERF_FTRACE_TRACE,
> > @@ -1254,6 +1272,12 @@ int cmd_ftrace(int argc, const char **argv)
> >   		goto out_delete_filters;
> >   	}
> > +	if (!is_ftrace_supported()) {
> > +		pr_err("ftrace is not supported on this system\n");
> > +		ret = -ENOTSUP;
> > +		goto out_delete_filters;
> > +	}
> > +
> 
> Very minor nit, but you could probably put this earlier next to
> check_ftrace_capable(). It didn't look like it used any of the config or
> parsing results.
>
Thansk, I will rebase this on perf-tools-next branch.

> Either way:
> 
> Reviewed-by: James Clark <james.clark@linaro.org>

-- 
Cheers,
Changbin Du

      reply	other threads:[~2024-09-11 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10  3:36 [PATCH] perf ftrace: Detect whether ftrace is enabled on system Changbin Du
2024-09-11  9:45 ` James Clark
2024-09-11 10:00   ` duchangbin [this message]

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=526bf9fecede4effa859214683201518@huawei.com \
    --to=changbin.du@huawei.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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).