lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Milian Wolff via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: Re: tracing page_faults with lttng?
Date: Sat, 02 Nov 2019 16:31:03 +0100	[thread overview]
Message-ID: <5848055.rMpeChdSCL__30707.6847109542$1572709277$gmane$org@agathebauer> (raw)
In-Reply-To: <3174598.JndGstr8t1@agathebauer>


[-- Attachment #1.1: Type: text/plain, Size: 1230 bytes --]

On Samstag, 12. Oktober 2019 23:31:51 CET Milian Wolff via lttng-dev wrote:
> On Montag, 29. Mai 2017 10:44:50 CEST Milian Wolff wrote:
> > On Wednesday, May 24, 2017 6:26:38 PM CEST Francis Deslauriers wrote:
> > > Hi Milian,
> > > Are you running on an x86 processor?
> > 
> > Yes, Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz.
> > 
> > > The pagefault tracepoints are called : x86_exceptions_page_fault_user,
> > > x86_exceptions_page_fault_kernel
> > > Can you see those tracepoints when you run: lttng list --kernel
> > 
> > Yes:
> > 
> > $ lttng list --kernel | grep fault
> > 
> >       x86_exceptions_page_fault_user (loglevel: TRACE_EMERG (0)) (type:
> > tracepoint)
> > 
> >       x86_exceptions_page_fault_kernel (loglevel: TRACE_EMERG (0)) (type:
> > tracepoint)
> > 
> >       kvm_async_pf_doublefault (loglevel: TRACE_EMERG (0)) (type:
> > tracepoint)
> 
> Hey there,
> 
> a follow up to the above question: What about tracing page faults on ARM?
> Perf can do that, but I see no page_fault trace points in the output of
> `lttng list -k`?

ping?

-- 
Milian Wolff | milian.wolff@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3826 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  parent reply	other threads:[~2019-11-02 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1807360.trHWC9KRqs@milian-kdab2>
2017-05-24 16:26 ` tracing page_faults with lttng? Francis Deslauriers
     [not found] ` <CADcCL0i-gZHviy_QZq_Krj_2zXiYvF-Z8BLu-3uQyA0anBfO-g@mail.gmail.com>
2017-05-29  8:44   ` Milian Wolff
     [not found]   ` <2312247.5OrstNElbn@milian-kdab2>
2019-10-12 21:31     ` Milian Wolff via lttng-dev
     [not found]     ` <3174598.JndGstr8t1@agathebauer>
2019-11-02 15:31       ` Milian Wolff via lttng-dev [this message]
     [not found]       ` <5848055.rMpeChdSCL@agathebauer>
2019-11-04 15:55         ` Francis Deslauriers
2017-05-24 16:00 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='5848055.rMpeChdSCL__30707.6847109542$1572709277$gmane$org@agathebauer' \
    --to=lttng-dev@lists.lttng.org \
    --cc=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;
as well as URLs for NNTP newsgroup(s).