From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Yang Jihong <yangjihong1@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, laoar.shao@gmail.com, rostedt@goodmis.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf sched: Fix record failed when CONFIG_SCHEDSTATS is not set
Date: Sun, 18 Jul 2021 10:37:46 -0300 [thread overview]
Message-ID: <YPQuqlhPP/mCKDu3@kernel.org> (raw)
In-Reply-To: <20210713112358.194693-1-yangjihong1@huawei.com>
Em Tue, Jul 13, 2021 at 07:23:58PM +0800, Yang Jihong escreveu:
> The tracepoints trace_sched_stat_{wait, sleep, iowait} are not exposed to user
> if CONFIG_SCHEDSTATS is not set, "perf sched record" records the three events.
> As a result, the command fails to be executed.
>
> Before:
>
> #perf sched record sleep 1
> event syntax error: 'sched:sched_stat_wait'
> \___ unknown tracepoint
>
> Error: File /sys/kernel/tracing/events/sched/sched_stat_wait not found.
> Hint: Perhaps this kernel misses some CONFIG_ setting to enable this feature?.
>
> Run 'perf list' for a list of valid events
>
> Usage: perf record [<options>] [<command>]
> or: perf record [<options>] -- <command> [<options>]
>
> -e, --event <event> event selector. use 'perf list' to list available events
>
> Solution:
> Check whether schedstat tracepoints are exposed. If no, these events are not recorded.
Thanks, applied.
- Arnaldo
prev parent reply other threads:[~2021-07-18 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 11:23 [PATCH] perf sched: Fix record failed when CONFIG_SCHEDSTATS is not set Yang Jihong
2021-07-18 13:37 ` Arnaldo Carvalho de Melo [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=YPQuqlhPP/mCKDu3@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=laoar.shao@gmail.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 \
--cc=rostedt@goodmis.org \
--cc=yangjihong1@huawei.com \
/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.