[lttng-dev] tracing page_faults with lttng?

Milian Wolff milian.wolff at kdab.com
Sat Oct 12 17:31:51 EDT 2019


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`?

Thanks

-- 
Milian Wolff | milian.wolff at kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL 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/20191012/92918ca5/attachment.bin>


More information about the lttng-dev mailing list