The cirros image was rebuilt against the 3.13.0-83 kernel, drivers e1000e, igbvf...
[packages/trusty/cirros-testvm.git] / cirros-testvm / src-cirros / buildroot-2015.05 / package / lttng-modules / Config.in
diff --git a/cirros-testvm/src-cirros/buildroot-2015.05/package/lttng-modules/Config.in b/cirros-testvm/src-cirros/buildroot-2015.05/package/lttng-modules/Config.in
new file mode 100644 (file)
index 0000000..e8ba9ba
--- /dev/null
@@ -0,0 +1,37 @@
+config BR2_PACKAGE_LTTNG_MODULES
+       bool "lttng-modules"
+       depends on BR2_LINUX_KERNEL
+       help
+         Linux kernel modules for the LTTng 2.x kernel tracing
+         infrastructure.
+
+         Make sure your target kernel has the following config
+         options enabled:
+
+           * CONFIG_MODULES: loadable module support
+           * CONFIG_KALLSYMS: 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 instrumentation features)
+
+         The following kernel configuration options will
+         affect the features available from LTTng:
+
+           * CONFIG_HAVE_SYSCALL_TRACEPOINTS: system call tracing
+           * CONFIG_PERF_EVENTS: performance counters
+           * CONFIG_EVENT_TRACING: needed to allow block layer tracing
+           * CONFIG_KPROBES: dynamic probes
+           * CONFIG_KRETPROBES: dynamic function entry/return probes
+           * CONFIG_KALLSYMS_ALL: state dump of mapping between block
+             device number and name
+
+         The packaged version is compatible with Linux 2.6.38 to 3.16.
+
+         http://lttng.org
+
+comment "lttng-modules needs a Linux kernel to be built"
+       depends on !BR2_LINUX_KERNEL