wrapper: remove random wrapper

[lttng-modules.git] / README.md

diff --git a/README.md b/README.md
index 17553e63346d96dbbaef254eb3de3b13ebf5e509..7d2515110c32e9d9e756e17b5d1016a52cb99051 100644 (file)
--- a/README.md
+++ b/README.md
@@ -59,9 +59,6 @@ Make sure your target kernel has the following config options enabled:
 
   - `CONFIG_MODULES`: loadable module support (not strictly required
      when built into the kernel),
-  - `CONFIG_KALLSYMS`: see files in [`wrapper`](wrapper); this is
-     necessary until the few required missing symbols are exported to GPL
-     modules from mainline,
   - `CONFIG_HIGH_RES_TIMERS`: needed for LTTng 2.x clock source,
   - `CONFIG_TRACEPOINTS`: kernel tracepoint instrumentation
      (enabled as a side-effect of any of the perf/ftrace/blktrace
@@ -91,9 +88,19 @@ available from LTTng:
 
         lttng enable-event -k --function ...
 
-  - `CONFIG_KALLSYMS_ALL`: state dump of mapping between block device
-    number and name
-
+Customization/Extension
+-----------------------
+
+The lttng-modules source includes definitions for the actual callback
+functions that will be attached to the kernel tracepoints by lttng.
+The lttng-modules project implements its own macros generating these
+callbacks: the LTTNG_TRACEPOINT_EVENT macro family found in
+instrumentation/events/lttng-module/. In order to show up in a
+lttng-modules trace, a kernel tracepoint must be defined within the
+kernel tree, and also defined within lttng-modules with the
+LTTNG_TRACEPOINT_EVENT macro family. Customizations or extensions must
+be done by modifying instances of these macros within the lttng-modules
+source.
 
 Usage
 -----