Skip to contentSkip to conversation

Fix: the clock plugin must be initiated before first use of the clock

PATCH Mathieu Desnoyers 1 participant 1 message Jul 22, 2016 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Mathieu Desnoyers

author Applied
#1 lore raw

Merged into lttng-modules master and stable-2.8, thanks!

Mathieu

Quoted 31 lines · ----- On Jul 22, 2016, at 9:56 AM, Anders Wallin [email protected] wrote:

When building lttng inside the kernel the clock plugin must be initated before the rest of the lttng code. Moved the module_init to rootfs_initcall. The functionality will not change when built as a module.

---
tests/clock-plugin/lttng-clock-plugin-test.c | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
tests/clock-plugin/lttng-clock-plugin-test.c +1 -1
index f16ea64..bf81932 100644
@@ -67,7 +67,7 @@ int lttng_clock_plugin_init(void)
 {
 	return lttng_clock_register_plugin(&ltc, THIS_MODULE);
 }
-module_init(lttng_clock_plugin_init);
+rootfs_initcall(lttng_clock_plugin_init);
 

static __exit
void lttng_clock_plugin_exit(void)
--
2.9.2

_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Signature · 7 lines
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev