From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] [RELEASE] LTTng modules 2.5.4 and 2.6.1
Date: Wed, 29 Apr 2015 15:17:42 +0000 (UTC) [thread overview]
Message-ID: <1873773903.40702.1430320662881.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1814803923.40695.1430320559235.JavaMail.zimbra@efficios.com>
Those releases cover bugfixes, and support for newer kernels (up
to 4.0) in the 2.6.1 release.
The LTTng modules provide Linux kernel tracing capability to the LTTng
2.x tracer toolset.
Changelogs:
2015-04-29 LTTng modules 2.5.4
* Fix: mmutrace warnings about redefined macros
* Fix: x86 mmutrace event extra field for kernels >= 3.11
* Fix: add missing x86 mmutrace kernel header include
* Fix: update README file to match reality: kernels >= 2.6.36 are supported
* Fix: add struct file_handle forward declaration
* Fix: atomic.h wrapper for kernels < 2.6.37
* Fix: disable x86 kvm instrumentation for kernels < 2.6.38
* Fix: mm_page_alloc_extfrag instrumentation for kernel 3.14.36
* Fix: update backported kmem patches to lttng-modules 2.5 API
* Fix: kmem instrumentation update for mm_page_alloc_extfrag kernel 3.19.2+
* Fix: kmem instrumentation: mm_page_alloc extfrag change_ownership field
2015-04-29 LTTng modules 2.6.1
* Fix: regmap build against kernel 4.0 kernel headers
* Fix: mmutrace warnings about redefined macros
* Fix: add missing x86 mmutrace kernel header include
* Fix: x86 mmutrace event extra field for kernels >= 3.11
* Fix: remove execute flag from kvm.h file
* Fix: build x86 kvm probes on kernels >= 4.1-rc1
* Fix: compilation warnings on 4.1-rc1 kernel
* Fix: compilation on 4.1-rc1 kernel, remove unused WB_WORK_REASON
* Fix: 4.1-rc1 Linux build and regmap instrumentation
* Fix: don't clash with older Debian kernel versions
* Fix: update get_pfnblock_flags_mask wrapper for debian kernels
* Fix: discover Debian API
* Fix: Update README.md to match reality: kernels >= 2.6.36 are supported
* Fix: add struct file_handle forward declaration
* Fix: atomic.h wrapper for kernels < 2.6.37
* Fix: disable x86 kvm instrumentation for kernels < 2.6.38
* Fix: check that class and instance prototype match
* Fix: lttng-events.h check function takes void
* Update regmap instrumentation for Linux 3.19.4 and 4.0
* Fix: kernels >= 2.6.33 put utsrelease.h in generated/
* Fix: Include utsrelease.h in lttng-kernel-version.h
* Fix: old kernels need module.h included before vermagic.h
* Fix: version condition in makefile
* Implement wrapper around get_pfnblock_flags_mask
* Fix: Support 4.x kernel versions in Makefile
* Fix: mm_page_alloc_extfrag instrumentation for kernel 3.14.36
* Fix: update writeback instrumentation for kernel 4.0+
* Fix: compaction mm_compaction_isolate_template update for Linux 4.0+
* Fix: kmem instrumentation update for mm_page_alloc_extfrag kernel 3.19.2+
* Fix: kmem instrumentation: mm_page_alloc extfrag change_ownership field
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-04-29 15:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1814803923.40695.1430320559235.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=1873773903.40702.1430320662881.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
/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