Skip to contentSkip to conversation

package/lttng-modules: enable CONFIG_FTRACE in kernel configuration

PATCH In review Thomas Petazzoni via buildroot 1 participant 3 messages Oct 12, 2022 – Nov 14, 2022

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 package/lttng-modules: enable CONFIG_FTRACE in kernel configuration

The build of lttng-modules will fail if the kernel does not have CONFIG_TRACEPOINTS enabled. However, CONFIG_TRACEPOINTS is a prompt-less option, and the most generic option that does enable CONFIG_TRACEPOINTS is CONFIG_FTRACE.

In addition, CONFIG_FTRACE will also enable CONFIG_STACKTRACE, which is needed on CPU architectures that don't provide the STACKWALK mechanism in the kernel, as is the case on ARM 32-bit for example.

Therefore, let's enable CONFIG_FTRACE when building lttng-modules.

---
 package/lttng-modules/lttng-modules.mk | 1 +
 1 file changed, 1 insertion(+)
package/lttng-modules/lttng-modules.mk +1 -0
index d527bc19ef..97cda53f08 100644
@@ -14,6 +14,7 @@ LTTNG_MODULES_MODULE_MAKE_OPTS = CONFIG_LTTNG=m CONFIG_LTTNG_CLOCK_PLUGIN_TEST=m
 
 define LTTNG_MODULES_LINUX_CONFIG_FIXUPS
 	$(call KCONFIG_ENABLE_OPT,CONFIG_KPROBES)
+	$(call KCONFIG_ENABLE_OPT,CONFIG_FTRACE)
 endef
 
 $(eval $(kernel-module))
Signature · 6 lines
2.37.3

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#1 lore raw

PATCH 2/2 package/lttng-modules: bump to 2.13.7

This is the latest point release in the stable 2.13 branch (currently the latest stable branch available).

---
 package/lttng-modules/lttng-modules.hash | 4 ++--
 package/lttng-modules/lttng-modules.mk   | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)
package/lttng-modules/lttng-modules.hash +2 -2
index fb253c9bf6..e685cc3367 100644
@@ -1,5 +1,5 @@
-# From https://lttng.org/files/lttng-modules/lttng-modules-2.13.1.tar.bz2.sha256
-sha256  a7c86d91c9bbe66d27f025aa04b8cfc6d7785ed2fc7ef774930800ee44d7f343  lttng-modules-2.13.1.tar.bz2
+# From https://lttng.org/files/lttng-modules/lttng-modules-2.13.7.tar.bz2.sha256
+sha256  5a99679df7903160cbde3918fee5af90ffafc90fc96ccdefaa57cf230492b234  lttng-modules-2.13.7.tar.bz2
 
 # Hash for license files
 sha256  d72921266bc8452a8789f8a04a82755373990d00b7e0b0f1a8edb8f854e94d1c  LICENSES/LGPL-2.1
package/lttng-modules/lttng-modules.mk +1 -1
index 97cda53f08..416833f4ef 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-LTTNG_MODULES_VERSION = 2.13.1
+LTTNG_MODULES_VERSION = 2.13.7
 LTTNG_MODULES_SITE = http://lttng.org/files/lttng-modules
 LTTNG_MODULES_SOURCE = lttng-modules-$(LTTNG_MODULES_VERSION).tar.bz2
 LTTNG_MODULES_LICENSE = LGPL-2.1/GPL-2.0 (kernel modules), MIT (lib/bitfield.h, lib/prio_heap/*)
Signature · 6 lines
2.37.3

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#2 lore raw
In reply to Thomas Petazzoni via buildroot
Quoted 9 lines · On Wed, 12 Oct 2022 22:23:16 +0200 Thomas Petazzoni via buildroot…

The build of lttng-modules will fail if the kernel does not have CONFIG_TRACEPOINTS enabled. However, CONFIG_TRACEPOINTS is a prompt-less option, and the most generic option that does enable CONFIG_TRACEPOINTS is CONFIG_FTRACE.

In addition, CONFIG_FTRACE will also enable CONFIG_STACKTRACE, which is needed on CPU architectures that don't provide the STACKWALK mechanism in the kernel, as is the case on ARM 32-bit for example.

Quoted 8 lines

Therefore, let's enable CONFIG_FTRACE when building lttng-modules.

---
 package/lttng-modules/lttng-modules.mk | 1 +
 1 file changed, 1 insertion(+)

Both applied to next!

Thomas

Signature · 7 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot