+3) Enable tracepoint event(s). Here for example, we want only
+'sched_switch' and 'sched_wakeup' events for the kernel (-k/--kernel).
+
+# lttng enable-event sched_switch,sched_wakeup -k
+
+or enable ALL tracepoint events:
+
+# lttng enable-event -a -k --tracepoint
+
+4) Enable all system call event(s).
+
+# lttng enable-event -a -k --syscall
+
+5) Enable kprobes and/or the function tracer with lttng
+
+This is a new feature made possible by the new LTTng 2.0 kernel tracer. You can
+enable a dynamic probe and data will be output in the trace along side with
+your tracing data.
+
+# lttng enable-event aname -k --probe symbol+0x0
+
+or
+
+# lttng enable-event aname -k --probe 0xffff7260695
+
+Either an <address> or a <symbol+offset> can be used for probes.
+
+You can also enable function tracer, which uses the Ftrace API (by Steven
+Rostedt). Again, data will be output in the trace.
+
+# lttng enable-event aname -k --function <symbol_name>
+
+6) Enable context information for an event:
+
+This is also a new feature which allows you to add context information to an
+event. For example, you can add the PID along with the event information:
+
+# lttng add-context -k -e sched_switch -t pid
+
+At this point, you will have to look at 'lttng add-context --help' for all
+possible context type which are integer values.
+
+You can on the same line activate multiple context:
+
+# lttng add-context -k -e sched_switch -t pid -t nice -t tid
+
+7) Enable perf counter for an event:
+
+Again, a new powerful feature is the possibility to add perf counter data
+(using the perf API by Ingo Molnar and Thomas Gleixner) to the trace on a per
+event basis. Let say we want to get the CPU cycles at each event:
+
+# lttng add-context -k -e sched_switch -t perf:cpu-cycles
+
+You'll have to use the add-context help for all possible perf counter values.
+
+8) Start tracing: