X-Git-Url: http://git.efficios.com/?p=lttng-tools.git;a=blobdiff_plain;f=src%2Fbin%2Flttng-sessiond%2Fmodprobe.c;h=a093f2412c4006d5c1660d2b6e12bdf2f3a74968;hp=cf9c12b3c81b5bfad2bf1d55ecab21fd3d8ddc81;hb=refs%2Fheads%2Fsow-2020-0002-rev1;hpb=3a4595c2469472dee1656cde5f8882c2123efd3c diff --git a/src/bin/lttng-sessiond/modprobe.c b/src/bin/lttng-sessiond/modprobe.c index cf9c12b3c..a093f2412 100644 --- a/src/bin/lttng-sessiond/modprobe.c +++ b/src/bin/lttng-sessiond/modprobe.c @@ -30,6 +30,10 @@ #define LTTNG_MOD_OPTIONAL 0 /* LTTng kernel tracer mandatory core modules list */ +/* TODO: the new trigger client might not be present in previous lttng-modules + * should it be optional? + * Can we reuse this to also know of the trigger feature is supported? + */ struct kern_modules_param kern_modules_control_core[] = { { (char *) "lttng-ring-buffer-client-discard" }, { (char *) "lttng-ring-buffer-client-overwrite" }, @@ -37,6 +41,9 @@ struct kern_modules_param kern_modules_control_core[] = { { (char *) "lttng-ring-buffer-client-mmap-discard" }, { (char *) "lttng-ring-buffer-client-mmap-overwrite" }, { (char *) "lttng-ring-buffer-metadata-mmap-client" }, + { (char *) "lttng-ring-buffer-trigger-client" }, + { (char *) "lttng-counter-client-percpu-64-modular" }, + { (char *) "lttng-counter-client-percpu-32-modular" }, }; /* LTTng kernel tracer probe modules list */