From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>
Cc: Masami Hiramatsu <masami.hiramatsu@linaro.org>,
rostedt@goodmis.org, mingo@redhat.com
Subject: File not found: /sys/kernel/debug/tracing/events/syscalls
Date: Tue, 27 Nov 2018 20:52:00 +0530 [thread overview]
Message-ID: <CA+G9fYvgDP2+D2mgqxJJJYm1DTgxbByxjKuVGBFOa-m_fT7Q-Q@mail.gmail.com> (raw)
While debugging the selftests/bpf: get_cgroup_id_user test failure on arm64
where the test is expecting trace file
/sys/kernel/debug/tracing/events/syscalls/sys_enter_nanosleep/id
but this path not enabled after enabling required kernel configuration also.
CONFIG_FTRACE_SYSCALLS=y
strace output:
open(\"/sys/kernel/debug/tracing/events/syscalls/sys_enter_nanosleep/id\",
O_RDONLY) = -1 ENOENT (No such file or directory)
This problem noticed on Linux mainline kernel version 4.20.0-rc3.
Best regards
Naresh Kamboju
next reply other threads:[~2018-11-27 15:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 15:22 Naresh Kamboju [this message]
2018-11-27 16:11 ` File not found: /sys/kernel/debug/tracing/events/syscalls Masami Hiramatsu
2018-11-27 16:29 ` [PATCH] arm64: ftrace: Fix to enable syscall events on arm64 Masami Hiramatsu
2018-11-27 16:32 ` Steven Rostedt
2018-11-27 16:58 ` Will Deacon
2018-11-27 18:18 ` Steven Rostedt
2018-11-27 23:55 ` Masami Hiramatsu
2018-11-28 12:05 ` Will Deacon
2018-11-28 14:22 ` Steven Rostedt
2018-11-28 19:59 ` Will Deacon
2018-11-29 5:38 ` Masami Hiramatsu
2018-11-29 5:39 ` [PATCH v2] " Masami Hiramatsu
2018-11-29 16:53 ` Catalin Marinas
2018-11-29 22:13 ` Masami Hiramatsu
2018-11-28 2:19 ` File not found: /sys/kernel/debug/tracing/events/syscalls Naresh Kamboju
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=CA+G9fYvgDP2+D2mgqxJJJYm1DTgxbByxjKuVGBFOa-m_fT7Q-Q@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=mingo@redhat.com \
--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 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).