From: duchangbin <changbin.du@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: James Clark <james.clark@linaro.org>,
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>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v2] perf ftrace: Detect whether ftrace is enabled on system
Date: Thu, 12 Sep 2024 09:54:35 +0000 [thread overview]
Message-ID: <b0d2446f5eed4c0b91cd853ea8033417@huawei.com> (raw)
In-Reply-To: <ZuGNhhzlTaAQaZXj@x1>
On Wed, Sep 11, 2024 at 09:31:02AM -0300, Arnaldo Carvalho de Melo wrote:
> On Wed, Sep 11, 2024 at 11:15:19AM +0100, James Clark wrote:
> > On 11/09/2024 11:01, 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".
>
> <SNIP>
>
> > > @@ -1583,6 +1601,11 @@ int cmd_ftrace(int argc, const char **argv)
> > > if (!check_ftrace_capable())
> > > return -1;
> > > + if (!is_ftrace_supported()) {
> > > + pr_err("ftrace is not supported on this system\n");
> > > + return -ENOTSUP;
> > > + }
> > > +
> > > ret = perf_config(perf_ftrace_config, &ftrace);
> > > if (ret < 0)
> > > return -1;
> >
> > Reviewed-by: James Clark <james.clark@linaro.org>
>
> Applied and added these comments:
>
> Committer testing:
>
> Doing it in an unprivileged toolbox container on Fedora 40:
>
> Before:
>
> acme@number:~/git/perf-tools-next$ toolbox enter perf
> ⬢[acme@toolbox perf-tools-next]$ sudo su -
> ⬢[root@toolbox ~]# ~acme/bin/perf ftrace
> failed to reset ftrace
> ⬢[root@toolbox ~]#
>
> After this patch:
>
> ⬢[root@toolbox ~]# ~acme/bin/perf ftrace
> ftrace is not supported on this system
> ⬢[root@toolbox ~]#
>
> Maybe we could check if we are in such as situation, inside an
> unprivileged container, and provide a HINT line?
>
I think we could check the mount status of tracefs first, and then check whether
the ftrace node exists. If there's a permission issue in container, maybe we
should also check the errno of access().
> Reviewed-by: James Clark <james.clark@linaro.org>
> Signed-off-by: Changbin Du <changbin.du@huawei.com>
> Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
--
Cheers,
Changbin Du
prev parent reply other threads:[~2024-09-12 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 10:01 [PATCH v2] perf ftrace: Detect whether ftrace is enabled on system Changbin Du
2024-09-11 10:15 ` James Clark
2024-09-11 12:31 ` Arnaldo Carvalho de Melo
2024-09-12 9:54 ` 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=b0d2446f5eed4c0b91cd853ea8033417@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).