From: milian.wolff@kdab.com (Milian Wolff)
Subject: [lttng-dev] tracing page_faults with lttng?
Date: Wed, 24 May 2017 18:00:47 +0200 [thread overview]
Message-ID: <1807360.trHWC9KRqs@milian-kdab2> (raw)
Hey all,
when I trace with perf, I can see page_faults occurring. But when I do
something like the following with lttng:
lttng create
lttng enable-channel kernel -k
lttng enable-event -c kernel -k -a
lttng start
# trigger page faults
lttng stop
then I do not see any page faults in tracecompass/babeltrace. What do I need
to do to see those too? I'm aware that lttng comes with its own set of
tracepoints - i.e. it's not using the same tracepoints that perf knows about.
But googling shows me e.g. this:
https://lists.lttng.org/pipermail/lttng-dev/2013-April/019954.html
https://lists.lttng.org/pipermail/lttng-dev/2016-May/026033.html
Which sounds like the feature should be available in lttng too?
I'm using the ArchLinux packages in AUR, i.e. version 2.9.2 of LTTng and
kernel 4.10.13-1.
Thanks
--
Milian Wolff | milian.wolff at kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3826 bytes
Desc: not available
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20170524/0c3796f4/attachment.bin>
next reply other threads:[~2017-05-24 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 16:00 Milian Wolff [this message]
2017-05-24 16:26 ` Francis Deslauriers
2017-05-29 8:44 ` Milian Wolff
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=1807360.trHWC9KRqs@milian-kdab2 \
--to=milian.wolff@kdab.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