+3) 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 Kprobe (by Masami Hiramatsu) and data will be output in the trace
+along side with your tracing data.
+
+# lttng enable-event aname --kprobe symbol+0xffff7260695
+
+or
+
+# lttng enable-event aname --kprobe 0xffff7260695
+
+Either an <address> or a <symbol+offset> can be used for kprobes.
+
+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 --function <symbol_name>
+
+4) 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 0
+
+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 0 -t 2 -t 4
+
+5) 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) to the trace on a per event basis. Let say
+we want to get the CPU cycles at each define event:
+
+# lttng add-context -k -e sched_switch --perf-name aname --perf-type 0 --perf-id 0
+
+You'll have to use the add-context help for all possible perf counter values.
+
+6) Start tracing: