From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev <lttng-dev@lists.lttng.org>
Cc: diamon-discuss@lists.linuxfoundation.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [diamon-discuss] [RELEASE] LTTng-modules 2.8.4 and 2.9.1 (Linux kernel tracer)
Date: Fri, 17 Feb 2017 17:23:54 +0000 (UTC) [thread overview]
Message-ID: <2014569414.67331.1487352234782.JavaMail.zimbra@efficios.com> (raw)
The LTTng modules provide Linux kernel tracing capability to the LTTng
tracer toolset.
Those are stable branch releases for stable-2.8 and stable-2.9 lttng-modules
branches. Version 2.9.1 adds support for the 4.10 version of the linux kernel
release candidates. The rest are various bugfixes.
Project website: http://lttng.org
Documentation: http://lttng.org/docs
Download link: http://lttng.org/download
Changelog:
2017-02-17 (National Cabbage Day) LTTng modules 2.9.1
* Fix: nmi-safe clock on 32-bit systems
* Fix: only include linux/cpuhotplug.h for kernels >= 4.10
* Fix: 4.10 hotplug adaptation backward compat
* Adapt lttng-modules to Linux 4.10 cpu hotplug state machine
* Fix: 4.10 btrfs instrumentation update backward compat
* Update btrfs instrumentation for 4.10 kernel
* btrfs instrumentation: update to 4.10 kernel
* timer instrumentation: adapt to ktime_t without union
* Fix: asoc instrumentation for RHEL 7.3
* Fix: SCSI instrumentation for SLES12 SP2
* Add SUSE Linux Enterprise kernel version tests
2017-02-17 (National Cabbage Day) LTTng modules 2.8.4
* Fix: nmi-safe clock on 32-bit systems
* Fix: asoc instrumentation for RHEL 7.3
* Fix: SCSI instrumentation for SLES12 SP2
* Add SUSE Linux Enterprise kernel version tests
* Fix: preemptible and migratable context error handling
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
reply other threads:[~2017-02-17 17:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2014569414.67331.1487352234782.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox