From: Steven Rostedt <rostedt@goodmis.org>
To: Trip Volpe <trip.volpe@gmail.com>
Cc: linux-trace-users@vger.kernel.org
Subject: Re: Missing exceptions:page_fault_user event?
Date: Mon, 26 Nov 2018 22:30:04 -0500 [thread overview]
Message-ID: <20181126223004.3e5e5c42@vmware.local.home> (raw)
In-Reply-To: <CANaP9wOV7nWjEwvef1B9dPCJfcvgFNwm1Nzt19_SzNnBEJLVqg@mail.gmail.com>
On Mon, 26 Nov 2018 18:49:19 -0800
Trip Volpe <trip.volpe@gmail.com> wrote:
> Hey all; I'm trying to use `perf record` to get detailed information
> about user page faults, including the addresses at which the faults
> occurred. I've done this before with, e.g., `perf record -e
> exceptions:page_fault_user -p 12345 sleep 1`.
>
> However, on the system I'm examining now, I just get an "unknown
> tracepoint" error. I checked
> /sys/kernel/debug/tracing/events/exceptions, and sure enough, that
I'm guessing that debugfs is mounted. What other event systems are
there?
# ls /sys/kernel/debug/tracing/event
What does the above produce?
-- Steve
> path does not exist. Does anybody happen to know under what
> circumstances these tracepoints could be disabled or omitted? I've
> looked through the kconfigs and sysctls for anything that might seem
> relevant but have had no luck so far.
>
> I'm running Ubuntu 16.04 with kernel 4.13 on a dual Xeon Gold 6126 system.
>
> # uname -a
> Linux test 4.13.0-37-generic #42~16.04.1 SMP Sat May 12 06:21:13 UTC
> 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> My kernel config is here: https://pastebin.com/raw/A62FDFd6
>
> Any help or pointers would be greatly appreciated!
next prev parent reply other threads:[~2018-11-27 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 2:49 Missing exceptions:page_fault_user event? Trip Volpe
2018-11-27 3:30 ` Steven Rostedt [this message]
[not found] ` <CANaP9wNqYQ4GUxg52cJNJTYhjj0eU4E19rcfyzH7PLU57Ks4OA@mail.gmail.com>
2018-12-02 22:15 ` Steven Rostedt
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=20181126223004.3e5e5c42@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=trip.volpe@gmail.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 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).