From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev@lists.lttng.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [RELEASE] LTTng modules 2.6.0 (Gaia)
Date: Mon, 26 Jan 2015 20:04:45 +0000 (UTC) [thread overview]
Message-ID: <1224618254.53158.1422302685749.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <314636431.53126.1422302376219.JavaMail.zimbra@efficios.com>
We are now releasing the 2.6.0 LTTng modules Linux kernel tracer.
New & Noteworthy features in the LTTng Linux kernel tracer 2.6.0:
- System call filtering! Fine-tune which system calls you want
to trace or not,
- We now gather in/out parameters of system calls at entry and
exit of the syscall. Please note that the system call event
semantic (naming) have changed in this release. You may have
to update your analysis if they depended on the old semantic,
- Trace NMI handlers, using the new NMI-safe clock monotonic
available in kernels >= 3.17.
Changelog since LTTng modules 2.6.0-rc2:
2015-01-26 LTTng modules 2.6.0
* Fix: missing parenthesis in offset_align_floor
* Fix: implement time.h wrapper for FD_ISSET
* Fix: update sched instrumentation for 3.19+ kernels
* Fix: update rcu instrumentation for 3.19+ kernels
* Fix: update scsi instrumentation for 3.19+ kernels
* Fix: update module instrumentation for 3.19+ kernels
* Fix: Add f_dentry wrapper for 3.19+ kernels
* Fix: introduce lttng_get_unused_fd() wrapper for 3.19 kernels
* Fix: lttng_this_cpu_ptr wrapper for kernel 3.19+
* Fix: Update btrfs instrumentation for 3.18 Linux kernel
* Fix compile error on kernel 3.0.101 with CONFIG_PERF_EVENTS
* Conditional compilation introduced by lttng-modules commit
Project website: http://lttng.org
Documentation: http://lttng.org/docs
Download link: http://lttng.org/download
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
parent reply other threads:[~2015-01-26 20:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <314636431.53126.1422302376219.JavaMail.zimbra@efficios.com>]
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=1224618254.53158.1422302685749.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
/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.