lttng-ust: efficient system-wide user-space tracing · 3 content overview of lttng 2.x and ust,...

1

LTTng-UST: Efficient System-Wide User-Space Tracing

Collaboration Summit 2013

christian.babeux@efficios.com @c_bab

2

whoami

Christian Babeux, Software Developer, EfficiOS,

Background in embedded and ASIC tools,

Active contributor to the LTTng projects:● lttng-tools & lttng-ust,● CI infra, Website, Twitter.

AUR package maintainer for Arch Linux.

3

Content

Overview of LTTng 2.x and UST,

User-space instrumentation sources,

Trace format standardisation efforts,

Tales from a user-space tracer,

Recent features & future work.

4

Overview of LTTng 2.xOverview of LTTng 2.x

5

Overview of LTTng 2.x

Unified user interface, API, kernel and user space tracers,

Trace output in a unified format,

Low overhead,

Shipped in distros: Ubuntu, Debian, Suse, Fedora, Linaro, Wind River, etc.

6

Project overview

7

Tracers

● lttng-modules: kernel tracer module, compatible with kernels from 2.6.38* to 3.9,

● lttng-ust: user-space tracer, in-process library.

* Kernel tracing is now possible on 2.6.32 to 2.6.37 by backport of 3 Linux Kernel patches [1].

8

Utilities

● lttng-tools: cli utilities and daemons for trace control,

– lttng: cli utility for tracing control,

– lttng-sessiond: tracing registry daemon,

– lttng-consumerd: consume trace data,

– lttng-relayd: network streaming daemon.

9

Viewers

● babeltrace: cli text viewer, trace converter, plugin system,

● lttngtop: ncurse top-like viewer,● Eclipse lttng plugin: front-end for lttng, collect,

visualize and analyze traces, highly extensible.

10

Overview of LTTng-USTOverview of LTTng-UST

11

LTTng-UST – Features

Pure userspace implementation,– Shared memory map between apps and trace

consumers,

– Portable to other OS: BSDs, Cygwin (experimental).

Optimized for low-overhead, high-throughput [2],

– Generic kernel ringbuffer ported to userspace,

– Efficient concurrent data structures for trace control.

12

LTTng-UST – Features (cont.)

Dynamically enabled, statically defined instrumentation,

Per user tracing and system-wide tracing,– Tracing group for system-wide tracing.

Traces recoverable even after application crash.

13

LTTng-UST – How does it work?

Users instrument their applications with static tracepoints,

liblttng-ust, in-process library, dynamically linked with application,

Session setup, etc.,

Run app, collect traces,

Post analysis with viewers.

14

Tracing session - Setup

$ lttng create

$ lttng enable-event -u -a

$ lttng start

Session setup

User-space event enabling

Start tracing

15

Tracing session - A wild app appears

● Listener thread spawned via constructor (GCC extension),

● App registration,

● Send SHM and wait fd.

16

Tracing session – App. execution & teardown

● App running,

● Events written to ringbuffer,

● Notification of data availability via pipe,

● App unregistered via destructor.

17

User-space instrumentation User-space instrumentation sourcessources

18

Tracepoints - DeclarationTRACEPOINT_EVENT( /* Provider name */ ust_tests_hello, /* Tracepoint name */

tptest,

/* Type, variable name */ TP_ARGS(int, anint,

long *, values, float, floatarg),

/* Type, field name, expression */ TP_FIELDS(ctf_integer(int, intfield, anint), ctf_array(long, arrfield1, values, 3), ctf_float(float, floatfield, floatarg)))

19

Tracepoints - Invocation

void function(void){

int i = 0; long vals[3] = { 0x42, 0xCC, 0xC001CAFE }; float flt = M_PI;

[...] tracepoint(ust_tests_hello,

tptest, i, &vals, flt);

[...]}

20

SystemTAP SDT Providers

Integration result of Collaboration Summit 2011 discussions,

Compatibility with SystemTAP SDT,– Users can use SystemTAP with tracepoint()

instrumented code.

21

Kernel patchset merged in 3.5,

LTTng integration:

– Initial lttng-modules patchset proposed [4],– Need usability improvement– Interface not exported by kernel

Uprobes

22

Trace format standardisation efforts

23

Trace format standardisation efforts

Source: xkcd.com/927

24

Trace format standardisation efforts

Joking aside: We need a common open format,

Collaboration: Multicore Association, Ericsson,

Goals of the Common Trace Format (CTF):– Common format for SW and HW traces,

– Portable,

– Compact,

Tools based on CTF:– LTTng 2.x, Babeltrace, Eclipse LTTng plugin

– GDB (save trace to CTF) [3],

– Javeltrace

25

Common Trace Format

Self-described, packet-based format.

26

Common Trace Format – More info.

“Interoperability Between Tracing Tools with the Common Trace Format”,

– Mathieu Desnoyers at Linux Plumbers 2012 [5]

Common Trace Format (CTF) Specification [6],

Common Trace Format compliance testsuite [7].

27

Tales from a user-space Tales from a user-space tracertracer

28

Non-intrusive handling of SIGPIPE

Ringbuffer delivery notification use a pipe,– Traced applications can receive SIGPIPE if

consumer end dies abruptly.

Suppress SIGPIPE only in our lib without affecting signal handling for the rest of the process [8].

29

TLS & constructors

● Thread Local Storage (TLS) variable storage in dynamically libs. allocated when first used [9],

● Rely on internal glibc mutex to protect against

dynamic linker,

● Same mutex is held while running ctor/dtor,

30

TLS & constructors (cont.)

31

TLS & constructors (cont.)

● Take mutex within constructors while TLS fixup performed,

Deadlock!

● Workaround: Force TLS fixup within lib ctor.

32

Tracing of apps closing all fds

33

Close all the things

● When daemonizing, some apps close all available fds,

34

Tracing of apps closing all fds

● When daemonizing, some apps close all available fds,

No communication == No tracing.

● Fix: None for the moment.

35

Recent features & future Recent features & future workwork

36

Recent features

2.1 (Basse Messe)

Network streaming over TCP,● Introduce lttng-relayd, receive traces from

remote consumers.

Filtering before data collection,● C-like syntax, bytecode interpreter.● UST only for the moment.

Session daemon health monitoring API.

37

Network streaming over TCP

38

Filtering (1)

Filter:

“(intfield > 42 && intfield <= 44) || longfield == 1”

39

Filtering (2)

“(intfield > 42 && intfield <= 44) || longfield == 1”

40

Recent features (cont.)

2.2 (Cuda, Currently in RC)

Per-uid buffers in UST,

Context filtering,● '$ctx.procname == “demo*”',● '$ctx.vpid > 9000'.

Trace file size limits,

41

Future work

Flight recorder mode tracing (2.3),

Trace data extracted on core dump (2.3),

Java tracing.

42

Future work (cont.)

Tracer triggers actions on specific events & filters

Compressed, encrypted streaming and storage,

LTTng accepted in Google Summer of Code [10].– Dynamic instrumentation support in UST,

– Android port.

43

Conclusion

Usability of user space tracing in production

44

Questions ?

? lttng.org

lttng-dev@lists.lttng.org

@lttng_project

www.efficios.com

45

References● [1] – Userspace tracing in small footprint devices – Jason Wessel

● [2] – lttng-modules README -

● [3] – [lttng-dev] [lttng-modules PATCH] Add uprobes support – Yannick Brosseau

● [4] – [PATCH v3 00/15] CTF Support – Yao Qi

● [5] - “Interoperability Between Tracing Tools with the Common Trace Format” - Mathieu Desnoyers, Linux Plumbers 2012

● [6] - Common Trace Format (CTF) Specification

● [7] - Common Trace Format compliance testsuite

● [8] – LTTng-UST – 2C44F5B9 - Fix UST SIGPIPE handling

● [9] – ELF Handling for Thread-Local Storage – Ulrich Drepper (page 8)

● [10] – LTTng GSoC 2013 Ideas list