archive mirror
 help / color / mirror / Atom feed
From: Trip Volpe <>
Subject: Missing exceptions:page_fault_user event?
Date: Mon, 26 Nov 2018 18:49:19 -0800	[thread overview]
Message-ID: <> (raw)

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
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:

Any help or pointers would be greatly appreciated!

             reply	other threads:[~2018-11-27 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27  2:49 Trip Volpe [this message]
2018-11-27  3:30 ` Steven Rostedt
     [not found]   ` <>
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: Missing exceptions:page_fault_user event?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).