From: Philippe Proulx <eeppeliteloop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/7] lttng-modules: bump to version 2.6.0
Date: Fri, 6 Mar 2015 12:35:54 -0500 [thread overview]
Message-ID: <1425663357-22541-5-git-send-email-eeppeliteloop@gmail.com> (raw)
In-Reply-To: <1425663357-22541-1-git-send-email-eeppeliteloop@gmail.com>
Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
---
package/lttng-modules/Config.in | 34 +++++++++++++++++++++++---------
package/lttng-modules/lttng-modules.hash | 8 ++------
package/lttng-modules/lttng-modules.mk | 2 +-
3 files changed, 28 insertions(+), 16 deletions(-)
diff --git a/package/lttng-modules/Config.in b/package/lttng-modules/Config.in
index 8cfa874..e8ba9ba 100644
--- a/package/lttng-modules/Config.in
+++ b/package/lttng-modules/Config.in
@@ -2,18 +2,34 @@ config BR2_PACKAGE_LTTNG_MODULES
bool "lttng-modules"
depends on BR2_LINUX_KERNEL
help
- Kernel modules for the LTTng 2.0 kernel tracing
+ Linux kernel modules for the LTTng 2.x kernel tracing
infrastructure.
- Your kernel must have CONFIG_TRACEPOINTS enabled for this
- package to build something useful. You may also want to have
- CONFIG_PERF_EVENTS to access perf event counters from
- ltt-ng. Note that system call tracing is only available on
- architectures that support CONFIG_HAVE_SYSCALL_TRACEPOINTS.
+ Make sure your target kernel has the following config
+ options enabled:
- The packaged version is compatible with kernel 2.6.38,
- 2.6.39, 3.0 and 3.1.0. See
- http://lttng.org/files/bundles/20111214/README.compatible.kernels.txt
+ * 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
diff --git a/package/lttng-modules/lttng-modules.hash b/package/lttng-modules/lttng-modules.hash
index 25dba0c..918b4cf 100644
--- a/package/lttng-modules/lttng-modules.hash
+++ b/package/lttng-modules/lttng-modules.hash
@@ -1,6 +1,2 @@
-# From http://lttng.org/files/lttng-modules/lttng-modules-2.5.1.tar.bz2.sha1
-sha1 75d9662ed3f8d7c53833663a5d89fe31c015b3ca lttng-modules-2.5.1.tar.bz2
-# From http://lttng.org/files/lttng-modules/lttng-modules-2.5.1.tar.bz2.md5
-md5 2d99bb7311ba92e82e3b675f0b8dee7d lttng-modules-2.5.1.tar.bz2
-# Locally generated
-sha256 962238175f0959ac71b97fdde144a3f76a84f63aea6b3645f94da88512bcccdb lttng-modules-2.5.1.tar.bz2
+# http://www.lttng.org/files/lttng-modules/lttng-modules-2.6.0.tar.bz2.sha1
+sha1 6402ec848e2a75250e04be35f0c49332bf37a388 lttng-modules-2.6.0.tar.bz2
diff --git a/package/lttng-modules/lttng-modules.mk b/package/lttng-modules/lttng-modules.mk
index 02ec202..6833ad2 100644
--- a/package/lttng-modules/lttng-modules.mk
+++ b/package/lttng-modules/lttng-modules.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LTTNG_MODULES_VERSION = 2.5.1
+LTTNG_MODULES_VERSION = 2.6.0
LTTNG_MODULES_SITE = http://lttng.org/files/lttng-modules
LTTNG_MODULES_SOURCE = lttng-modules-$(LTTNG_MODULES_VERSION).tar.bz2
LTTNG_MODULES_LICENSE = LGPLv2.1/GPLv2 for kernel modules; MIT for lib/bitfield.h and lib/prio_heap/*
--
2.2.1
next prev parent reply other threads:[~2015-03-06 17:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 17:35 [Buildroot] [PATCH 0/7] General LTTng packages maintenance Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 1/7] liburcu: bump to version 0.8.6 Philippe Proulx
2015-03-06 22:21 ` Thomas Petazzoni
2015-03-06 17:35 ` [Buildroot] [PATCH 2/7] lttng-tools: bump to version 2.6.0 Philippe Proulx
2015-03-06 22:21 ` Thomas Petazzoni
2015-03-06 17:35 ` [Buildroot] [PATCH 3/7] lttng-libust: " Philippe Proulx
2015-03-06 22:24 ` Thomas Petazzoni
2015-03-07 0:33 ` Philippe Proulx
2015-03-06 17:35 ` Philippe Proulx [this message]
2015-03-06 22:28 ` [Buildroot] [PATCH 4/7] lttng-modules: " Thomas Petazzoni
2015-03-07 0:35 ` Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 5/7] lttng-babeltrace: update Config.in's help Philippe Proulx
2015-03-06 22:30 ` Thomas Petazzoni
2015-03-06 17:35 ` [Buildroot] [PATCH 6/7] lttng-libust: rename package to lttng-ust Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 7/7] lttng-babeltrace: rename package to babeltrace Philippe Proulx
2015-03-06 22:32 ` [Buildroot] [PATCH 0/7] General LTTng packages maintenance Thomas Petazzoni
2015-03-07 1:02 ` Arnout Vandecappelle
2015-03-07 7:59 ` Thomas Petazzoni
2015-03-07 20:50 ` Philippe Proulx
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1425663357-22541-5-git-send-email-eeppeliteloop@gmail.com \
--to=eeppeliteloop@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.