We need to backport three patches from the lttng upstream tree to
fix the build against 5.19+.
Obviously we'll drop these once the next lttng-modules release is
available.
(From OE-Core rev: dce3c772efab4e51a82fb9c8fb74bc614ee3a82e)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop backports; one of them (0009) is present only
on the master branch and not on 2.13 branch, and so
stays in the recipe.
(From OE-Core rev: 1002941b76e0a0351e85a20e3e8d0a6a2254449c)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* add missing space to fix:
/bin/sh: 1: [: Illegal number: 119)
shown in the log.do_compile (isn't fatal for the build)
(From OE-Core rev: 8f785f35c8a9cdc0107fbaa76b20df5199159ee0)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The following kernel commit has been back ported to v5.10.119 and v5.15.44.
commit 14c174633f349cb41ea90c2c0aaddac157012f74
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date: Thu Feb 10 16:40:44 2022 +0100
random: remove unused tracepoints
These explicit tracepoints aren't really used and show sign of aging.
It's work to keep these up to date, and before I attempted to keep them
up to date, they weren't up to date, which indicates that they're not
really used. These days there are better ways of introspecting anyway.
Which causes the following build failure
lttng-modules-2.13.3/src/probes/lttng-probe-random.c:18:10: fatal error: trace/events/random.h: No such file or directory
| 18 | #include <trace/events/random.h>
| | ^~~~~~~~~~~~~~~~~~~~~~~
| compilation terminated.
(From OE-Core rev: c8effd12cae7c7024f8e6c8f6ef70ed602d380ed)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
lttng-modules fails to build against 5.18-rc7, the details of the fix
are as follows:
The commit [fix: sched/tracing: Don't re-read p->state when emitting
sched_switch event (v5.18)] was correct, but the kernel changed their
mind with the following commit:
commit 9c2136be0878c88c53dea26943ce40bb03ad8d8d
Author: Delyan Kratunov <delyank@fb.com>
Date: Wed May 11 18:28:36 2022 +0000
sched/tracing: Append prev_state to tp args instead
Commit fa2c3254d7cf (sched/tracing: Don't re-read p->state when emitting
sched_switch event, 2022-01-20) added a new prev_state argument to the
sched_switch tracepoint, before the prev task_struct pointer.
This reordering of arguments broke BPF programs that use the raw
tracepoint (e.g. tp_btf programs). The type of the second argument has
changed and existing programs that assume a task_struct* argument
(e.g. for bpf_task_storage access) will now fail to verify.
If we instead append the new argument to the end, all existing programs
would continue to work and can conditionally extract the prev_state
argument on supported kernel versions.
Fixes: fa2c3254d7cf (sched/tracing: Don't re-read p->state when emitting sched_switch event, 2022-01-20)
Signed-off-by: Delyan Kratunov <delyank@fb.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Link: https://lkml.kernel.org/r/c8a6930dfdd58a4a5755fc01732675472979732b.camel@fb.com
By reordering the parameters (again) we can get back up and building.
Upstream-Status: Backport
(From OE-Core rev: fb69e5cfb043a15354beb2d613772aa0233d12ae)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Backporting changes from lttng master to support building against
the 5.18+ kernel. No changes required to the patches. Once a new
-stable 2.13.x is released, we can drop these patches. To enable
newer kernel development against the LTS, it is worth pulling these
in while we wait for an upstream release.
(From OE-Core rev: 8a7237a47488442513741930ea55d69dd6bd7be4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To fix the build against v5.17+ kernels, we backport 7 patches
from the lttng-modules upstream repository.
If a 2.13.2 lttng-modules release is done before the upcoming
release, we'll obviously drop these patches.
(From OE-Core rev: 4783a0fd9f86a0247a44b07bdb7e733e57c6664f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping lttng-modules to 2.13.1, which fixes the build against 5.16+
kernels.
We drop two previously backported patches.
The following commits are part of this update:
8c0aec7e Version 2.13.1
533556cd fix: mm: move kvmalloc-related functions to slab.h (v5.16)
2f0087ab fix: block: don't call blk_status_to_errno in blk_update_request (v5.16)
9b092ff2 fix: KVM: MMU: change tracepoints arguments to kvm_page_fault (v5.16)
036297af fix: KVM: x86: Get exit_reason as part of kvm_x86_ops.get_exit_info (v5.16)
a029f2a3 fix: isystem: delete global -isystem compile option (v5.16)
d82de6f3 fix: block: move block-related definitions out of fs.h (v5.16)
4fabf854 Fix: syscall tracing: missing trigger actions
38b35aff Warn on event registration/unregistration failure
e26f740b fix: implicit-int error in EXPORT_SYMBOL_GPL
c570be0d fix: Revert "Makefile: Enable -Wimplicit-fallthrough for Clang" (v5.15)
8be4c8a3 fix: cpu/hotplug: Remove deprecated CPU-hotplug functions. (v5.15)
(From OE-Core rev: 2edeebed4ff172f77e337af82fc1cddc681881df)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When testing linux-yocto-dev 5.15-rc, lttng-modules fails to build.
Upstream already has fixes for 5.15 in the release branch, so we
backport the two patches here and we can drop them on the next version
bump.
(From OE-Core rev: af17b507009be14d6f7069d39feb1fbd7563471d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was updated
with the 2.13.0 update (commit 5dad15af), but unfortunately it no
longer did what it was intended to do. There is also
0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch, which
was based on the former patch, but it too does not solve the problem.
Unify the two patches, and actually disable building of the kernel
module if CONFIG_TRACEPOINTS is not enabled, the way it was intended.
(From OE-Core rev: f2411917c09a31d154d29060f6c7e4ce7d544fc7)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating to 2.13.0, so we can pick up the latest -stable and
support for 5.14+ kernels.
We refresh one patch for new context, and update the LICENSE
checksum due to commit 2df37e95fa4303 [Cleanup: Move headers from
toplevel to include/lttng/]. which impacted the LICENSE file (but
licensing is the same).
MODULES_MODULE_SYMVERS_LOCATION must also be specified in this
release, as the lttng build has moved the module target to a
'src' subdirectory.
(From OE-Core rev: 5dad15af8b3423ad9631edf3eef6e77902f1b36e)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To support building against v5.12+ and v5.13+ kernels, bumping to the
v2.12.6 lttng-release.
We drop the previously backported patches, and bring in the following
commits:
0d8e4ab9 Version 2.12.6
78f56ae3 fix: adjust ranges for RHEL 8.2 and 8.3
4c996ea7 Disable block rwbs bitwise enum in default build
4ac46085 Disable sched_switch bitwise enum in default build
5e22c27b Add experimental bitwise enum config option
937d307e Add defaults to Kconfig options
4a114d43 Sync `show_inode_state()` macro with upstream stable kernels
3bd6ac3e fix: block: remove disk_part_iter (v5.12)
8bbb8c9d Fix: Backport of "Fix: increment buffer offset when failing to copy from user-space"
30cddf69 Fix: increment buffer offset when failing to copy from user-space
4733b9ab Sync `show_inode_state()` macro with Ubuntu 4.15 kernel
ff21ec48 fix: mm, tracing: kfree event name mismatching with provider kmem (v5.12)
b2b02c29 Set 'stable-2.12' branch in git review config
00b42dbf fix backport: block: add a disk_uevent helper (v5.12)
771ff089 fix: Adjust ranges for Ubuntu 5.4.0-67 kernel
d8933959 fix: block: add a disk_uevent helper (v5.12)
71034df1 Fix: properly compare type enumeration
4d879d23 compiler warning cleanup: is_signed_type: compare -1 to 1
fead3a9c Fix: bytecode linker: validate event and field array/sequence encoding
92cc3e7f Fix: kretprobe: null ptr deref on session destroy
49c603ef fix: mm, tracing: record slab name for kmem_cache_free() (v5.12)
23a2f61f Fix: filter interpreter early-exits on uninitialized value
b3fdf78b Fix: memory leaks on event destroy
(From OE-Core rev: c2f027b8e2f842915a0ffdfd6c2c0597f3b02bce)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To support builds against v5.13+ kernels, bumping the devupstream
to 2.13 and the 2.13-rc series.
Along with the SRCREV update, a port of the existing CONFIG_TRACEPOINTS
patch from the main Makefile to src/Kbuild is done.
The LICENSE file was part of commit [Cleanup: Move headers from toplevel
to include/lttng/], so we adjust the checksum to the new fie contents.
(From OE-Core rev: 18bf7b0eafc5331b0b33c0ae777374e24df741b8)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add the following patches from stable-2.12 branch of lttng repository
to fix errors when building lttng-modules against 5.12+ kernel
since they are not present on the release 2.12.5:
- 17cd2dc9 fix: block: add a disk_uevent helper (v5.12)
- 127135b6 fix backport: block: add a disk_uevent helper (v5.12)
- 853d5903 fix: mm, tracing: kfree event name mismatching with
provider kmem (v5.12)
(From OE-Core rev: 2538ba2b3490e3599d9ccd637aa8486ea428f1b0)
Signed-off-by: Vinicius Aquino <vinicius.aquino@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are four changes in addition to the 2.12.5 release that we
need to build against the 5.12 kernel. Rather than only rely on
people knowing to use devupstream support to build against newer
kernels, we backport the 4 patches while waiting for release.
(From OE-Core rev: 2d45c09bfbad969549c719654f72714324299f00)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We'd appear to be past the need for a gcc7 patch from 3 years ago now.
(From OE-Core rev: 1ff0eb404819d259c411937bd12c82e04a5837ba)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
lttng-modules doesn't currently build against the lastest 5.10-rc
versions.
Upstream lttng does have fixes for the issues, but hasn't done a
release that contains them yet. There are other patches on the
2.12.x branch, but I've skipped them for now as they aren't
necessary for 5.10 builds, and can be picked up with the next
full update.
We also bump the dev-upstream hash to make them easier to pickup
for those building from git.
(From OE-Core rev: 47201e98bb293d59c5d41986d066fd7614b914fa)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Backporting the 10 patches since the lttng 2.12.2 release. We'll drop
them once .3 is released, but for now, we need the fixes to build
against the latest 5.4, 5.8 and 5.9 kernels.
We also bump the devupstream SRCREV to pickup the same changes.
(From OE-Core rev: 62c87d1a68c4f7c8f30c3c5330dcda9cbcbbbaa7)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop backports.
devupstream variant was incorrectly updated in a059fc67da
(changed to 2.12, but without updating SRCREV), so revert it back
to 2.11.2.
(From OE-Core rev: 64e27ce04c4acb68c946804627e5c594b73052cb)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix the following warnings introduced after backporting linux kernel commit [1]
to stable branches:
# lttng create session
...
[ 483.242037] LTTng: vmalloc_sync_all symbol lookup failed.
[ 483.257056] Page fault handler and NMI tracing might trigger faults.
...
These patches should be dropped when a new stable 12.0 release is available.
[1] 763802b53a
(From OE-Core rev: f2e48f9127aee949364696315e3adc861aba1dd6)
Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
lttng hasn't released 2.10.9, but the stable/2.10 branch
contains changes that we need to build against the 5.0
kernel.
We add them here as patches, and we can drop them in the
future when lttng is updated.
(From OE-Core rev: f8bcf3486d44ebd867e9089d4dbd3b56726c9075)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Commit "f63965c0f9fc lttng: uprev to 2.10.7" dropped
0001-Fix-btrfs-Remove-unnecessary-fs_info-parameter.patch
from recipe, but left the patch itself in source tree.
Remove this patch since nobody uses it.
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>
(From OE-Core rev: 918c67a3fafbe4b77bab379ff652a986044b7a79)
Signed-off-by: Ruslan Bilovol <ruslan.bilovol@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto-dev has been upreved to v4.19. This patch backports a patch from
upstream to make lttng-modules sync up with linux-yocto-dev and later
linux-yocto, and fix the following do_compile error.
| tmp/work/qemux86_64-poky-linux/lttng-modules/2.10.7-r0/lttng-modules-2.10.7/probes/../probes/lttng-tracepoint-event-impl.h:143:6: error: conflict
ing types for 'trace_sock_exceed_buf_limit'
| void trace_##_name(_proto);
| ^~~~~~
(From OE-Core rev: d06b7fd291076a423a83b9630471baeaef9d4f43)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Building lttng-modules with linux-yocto-dev will cause do_compile
failure:
lttng-modules/2.10.6-r0/lttng-modules-2.10.6/probes/../probes/lttng-tracepoint-event-impl.h:143:6: error: conflicting types for 'trace_btrfs_reserve_extent'
void trace_##_name(_proto);
^~~~~~
The following commit from latest mainline kernel changes some btrfs
functions' prototype.
3dca5c942dac60164e6a6e89172f25b86af07ce7
"btrfs: trace: Remove unnecessary fs_info parameter for btrfs__reserve_extent event class"
This patch backports a commit from upstream to meet the above changes.
51ab0b1da29354375a19f865abcd233dd2178295
"Fix: btrfs: Remove unnecessary fs_info parameter"
(From OE-Core rev: c1daa5c0b89cdfab15d2fa093b021b2ce0937dad)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This upgrade is critical as it fixes the support for Linux 4.14 LTS kernel.
The changlog is:
2017-10-05 LTTng modules 2.9.5
* Fix: update block instrumentation for 4.14 kernel
* Revert "Fix: update block instrumentation for kernel 4.14"
2017-10-03 (National Techies Day) LTTng modules 2.9.4
* Fix: version check error in btrfs instrumentation
* Fix: update btrfs instrumentation for kernel 4.14
* Fix: update writeback instrumentation for kernel 4.14
* Fix: update block instrumentation for kernel 4.14
* Fix: vmalloc wrapper on kernel < 2.6.38
* Fix: vmalloc wrapper on kernel >= 4.12
* Add kmalloc failover to vmalloc
* Fix: mmap: caches aliased on virtual addresses
* Fix: update ext4 instrumentation for kernel 4.13
* Fix: Sleeping function called from invalid context
* Fix: sched for v4.11.5-rt1
* Fix: handle missing ftrace header on v4.12
This also removes the previously backported patches as they are part
of 2.9.4 release and the missing fix is part of 2.9.5 release.
(From OE-Core rev: 3ca3f8b2dbf0fec6a188ee2c10238704e4642c93)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This backport fixes from upcoming 2.9.4 release. Those are:
- Fix: vmalloc wrapper on kernel < 2.6.38
- Fix: vmalloc wrapper on kernel >= 4.12
- Add kmalloc failover to vmalloc
- Fix: mmap: caches aliased on virtual addresses
- Fix: update ext4 instrumentation for kernel 4.13
- Fix: Sleeping function called from invalid context
- Fix: sched for v4.11.5-rt1
- Fix: handle missing ftrace header on v4.12
This fix failures in some BSP layers which are using Linux 4.13
already.
(From OE-Core rev: 45ab93e74252f40dbe777000e1b33f4b3783536e)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix a variety of spelling and format mistakes to improve the ease of reading the
tags programatically.
(From OE-Core rev: 6e1aaf80b0d951b48cd25cb7161ec19448295094)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Avoid using LTTng's BUILD_RUNTIME_BUG_ON macro, as it appears to run
into a similar problem as Linux experienced with __builtin_constant_p
and dead code elimination.
(From OE-Core rev: 22af48a50d40d6872adaa4f6b0bf144ef5781c1c)
Signed-off-by: Nathan Lynch <nathan_lynch@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The lttng-modules are being pulled by the tools-profile image feature,
however, not every kernel has the CONFIG_TRACEPOINTS feature enabled.
This change makes the build do not fail when CONFIG_TRACEPOINTS is not
available, allowing it to be kept being pulled by default.
(From OE-Core rev: 6215ffec6a3d5069cc74ae9853167c3c6395b1db)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The lttng-modules Makefile allows us to specify the kernel we're
building against via the KERNELDIR variable on the build command line.
Use that and drop the patch (which tends to need updating whenever the
upstream Makefile changes).
(From OE-Core rev: cc6f6f96b668f7ef3db0f83c7d3585d81c569d31)
Signed-off-by: Nathan Lynch <nathan_lynch@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixes a build issue with the 3.19.5 kernel where the regmap prototypes
have changed. The patch is rebased do to changes in the new version of the
Makefile.
[YOCTO #7737]
(From OE-Core rev: 787fde133c6b50c5df6ce8f90b2906b7955b41e4)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To fix build issues against the v3.19 kernel, we can safely update to
the lttng 2.6 stable branches.
This allows us to drop two backported patches that are already part of
this update.
(From OE-Core rev: 76668418a63d4c0618c63bd9d13970df35e736eb)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This update the source code to the 2.5.2 version and also brings two
fixes from stable-2.5 branch. The update also allowed the removal of
some already applied patches from the metadata.
Doing this update, it fixes following build error:
,----
| make[1]: Entering directory `.../build-framebuffer/tmp/sysroots/imx23evk/usr/src/kernel'
|
| ERROR: Kernel configuration is invalid.
| include/generated/autoconf.h or include/config/auto.conf are missing.
| Run 'make oldconfig && make prepare' on kernel src to fix it.
|
| Building modules, stage 2.
| ./scripts/Makefile.modpost:42: include/config/auto.conf: No such file or directory
| make[2]: *** No rule to make target `include/config/auto.conf'. Stop.
| make[1]: *** [modules] Error 2
| make[1]: Leaving directory `.../build-framebuffer/tmp/sysroots/imx23evk/usr/src/kernel'
| make: *** [default] Error 2
`----
(From OE-Core rev: e575ab81f0cf145503c4afd9ce62040721a526b2)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-stable integrated the 3.16 commit f8c9301fa5a2a [mm/compaction: do
not count migratepages when unnecessary] with the 3.14.25 update.
So we have to update the lttng-module linux version codes to use the
new definition in builds greater than 3.14.24 or 3.16.
(From OE-Core rev: cf76820379746e91fc4cf01895cb98cc56987002)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The lttng-modules recipe was failing for meta-intel BSPs with the v3.17 kernel.
These BSP kernels were enabling some of the audio codec drivers, whose
structures are changed recently, causing mismatch with lttng-modules code
expectations. The qemu machines did not see this issue as they were not
enabling these sound codec kernel configuration.
Fix the build issue, by changing the lttng-modules code to match with
the structures used by the v3.17 kernel. The code is conditional on the
kernel version, that way it keeps working with the older kernel versions.
(From OE-Core rev: 1854d6c2e6dda4fd6900399d827413fcc1e1aef6)
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the lttng-modules 2.5 recipe with backports from the master branch to
enable builds on 3.17 based kernels.
(From OE-Core rev: cc2ef9b0f6371837faa5e430c0b6c48bf24a8c4c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
During the uprev of the yocto kernel to 3.16, lttng-modules failed to build.
To grab the latest stable content, we update to 2.5.0, and add two patches
to also make it build against 3.16+.
We also drop the older 2.3.3 lttng-modules, since it is no longer required
to support ARM builds.
(From OE-Core rev: 10680c8f06c52b25ed63d315596707701402646d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Apply the change "lttng-modules: Fix 3.14 bio tracepoints" to
2.3.3 as well as 2.4.0.
(From OE-Core rev: a419ad43a5b3aa5bc3aa095af4d79abe4c24b0d7)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the structure to work with immutable bio_vecs
(From OE-Core rev: 09d3d8f97d6c60707b8dfb3fa5b04fa2efe6f6f6)
(From OE-Core rev: b32d57e5a807a634c411628af1688aec960ac6e7)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
*This updates lttng-modules for 2.4.1 and
it also fixes the build with 3.13 Linux kernel.
(From OE-Core rev: 023c2401677f9af6895887d6e8bca2fd1d730985)
Signed-off-by: Chunrong Guo <B40290@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
