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>
Updating lttng-devupstream so we can build against kernel
5.9+
(From OE-Core rev: 11cf6562cf785d79da1f97257dcca93e75f37055)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some platforms support kernel tracing, some support userspace tracing.
This change:
* Moves the knowledge/config to one place in an inc file
* Allows lttng-tools to build without lttng-modules
* Hence enables tools+ust for riscv64
* Has the packagegroup just depend on lttng-tools which will pull in
ust/modules as needed
(From OE-Core rev: 1824cf062df928de65c1bff5e86e26b7b4d9d784)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since lttng-modules are not buildable, there is no point of building
tools either
(From OE-Core rev: 7138f09da4f3c523d4028fbe5b53923ad2b59a71)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Kernel 5.8+ and lttng requires kprobes and riscv64 lacks kprobes
Invert the COMPATIBLE_HOST regexp, as we support most of arches
(From OE-Core rev: 5a0096f3a2c268233c192deb455da67d2784afa4)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating to the 2.12.2 lttng-modules release. This is the standard
collection of bug fixes as well as changes to support building against
the v5.8 kernel.
Changelog follows:
2020-08-04 (National Chocolate Chip Cookie Day) LTTng modules 2.12.2
* Fix: Lock metadata cache on session destroy
* Fix: metadata stream leak, missing list removal and locking
* Fix: coherent state not changed atomically with metadata written
* fix: include module.h for EXPORT_SYMBOL_GPL
* fix: __lttng_vmalloc_node_range const caller introduced in v3.6
* fix: version range for overflow_callback
* fix: global_dirty_limit was introduced in v3.1
* fix: wrapper_uprobe_unregister is a void function
* fix: prior to v4.0, __vmalloc_node_range had no vm_flags param
* fix: vmalloc on v5.8 without KALLSYMS
* Detect missing symbols used with kallsyms_lookup at compile time
* Use exported symbol bdevname() instead of disk_name()
* Add git-review config
* fix: mm: remove vmalloc_sync_(un)mappings() (v5.8)
* fix: mm/writeback: discard NR_UNSTABLE_NFS, use NR_WRITEBACK (v5.8)
* fix: block: remove the error argument to the block_bio_complete (v5.8)
* fix: pipe_buf_operations rework (v5.8)
(From OE-Core rev: 08532e86d4c50e4d9ff99b4bb60f88ec3f5fc239)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To build against the v5.8-rc kernels, we need to pickup the latest
lttng-modules commits.
Bumping the devupstream version and SRCREV to do just that. Validated
against v5.8-rc4.
(From OE-Core rev: f743dfdb8f4b826bf64935720418cc30566b97ac)
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>
Upgrade lttng-tools 2.11.2 -> 2.12.0:
* drop x32 patch, as it was merged upstream
* update ptest file mi-lttng-3.0.xsd -> mi-lttng-4.0.xsd
* add local patch to fix ptest build failure on musl
* License-Update: licenses were moved under LICENSES directory and changed in
upstream commit [1]
[1] ab5be9fa2e
(From OE-Core rev: 62357f16ecc8368cf8a92290e973633622cd6368)
Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.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>
Upgrade to version 2.11.2 in order to fix some build errors
with latest 5.4 kernel.
- conflicting types for 'trace_fast_page_fault'
Reproductible on kernel greater than v5.4.19, starting with commit
8a1cd01bee ("KVM: x86: Use gpa_t for cr2/gpa to fix TDP support on
32-bit KVM")
Error messages:
lttng-modules-2.11.1/probes/../probes/lttng-tracepoint-event-impl.h:130:6:
error:
130 | void trace_##_name(_proto);
tmp/work-shared/axxiax86-64/kernel-source/include/linux/tracepoint.h:233:21:
note: previous definition of 'trace_fast_page_fault' was here
233 | static inline void trace_##name(proto)
- conflicting types for 'trace_rcu_dyntick'
Reproductible on kernel greater than v5.4.22, starting with commit
6cf539a87a ("rcu: Fix data-race due to atomic_t copy-by-value")
Error messages:
lttng-modules-2.11.1/probes/../probes/lttng-tracepoint-event-impl.h:130:6:
error: conflicting types for 'trace_rcu_dyntick'
130 | void trace_##_name
tmp/work-shared/axxiax86-64/kernel-source/include/linux/tracepoint.h:233:21:
note: previous definition of 'trace_rcu_dyntick' was here
233 | static inline void trace_##name(proto)
(From OE-Core rev: 8fcc33aea08fc1e82818893feb7b01c7cc1e6416)
Signed-off-by: Daniel Dragomir <Daniel.Dragomir@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When add below line to local.conf to enable debug build:
DEBUG_BUILD = "1"
There comes below failure when run "bitbake babeltrace2"
| ../../../../../git/src/plugins/ctf/fs-src/fs.c: In function 'ds_index_insert_ds_index_entry_sorted':
| ../../../../../git/src/plugins/ctf/fs-src/fs.c:702:5: error: 'other_entry' may be used uninitialized in this function [-Werror=maybe-uninitialized]
| 702 | !ds_index_entries_equal(entry, other_entry)) {
So initialize the other_entry pointer to fix the above error.
(From OE-Core rev: 1b98db372a1fdaecf9bb897b0ee4b2e72af22f81)
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Babeltrace 1 vs. Babeltrace 2
The Babeltrace project exists since 2010. In 2020, Babeltrace 2 was released.
Babeltrace 2 is a complete rewrite of the library, Python bindings, and CLI. It
is plugin based and offers much more features and potential than Babeltrace 1.
Because Babeltrace 2 is still a young released project, some distributions still
provide packages for the Babeltrace 1 project. Both projects can coexist on the
same system as there are no common installed files.
(From OE-Core rev: be52889ba5e5a2cf02f50b3f3acee8ca72ec494d)
Signed-off-by: Anders Wallin <wallinux@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
version 2.x.x will be added with a new babeltrace2 recipe
(From OE-Core rev: 0616a5dbc61561fefcd1822ce263837437466df2)
Signed-off-by: Anders Wallin <wallinux@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream is aware, and will investigate and fix.
(From OE-Core rev: 96c286a1b2f9fc8e8bf4fb29ae62551a323af5c3)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update: formatting, dropped the gpl texts, as they're
not anymore in source tree, and the main file is specific enough.
(From OE-Core rev: 15ca6acb87299ffc770d35b075024f0ccaace61f)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove 0001-Skip-when-testapp-is-not-present.patch as it is unclear
whether it needs to be rebased, and difficult to rebase.
Remove 0001-check-for-gettid-API-during-configure.patch as it
is no longer needed.
Ptests still seem to run ok, however they are rather slow,
so I did not wait for their completion.
(From OE-Core rev: 015aea5d93614676decd18578a8ae2d68417cfc5)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When using devupstream class the SRCREV_FORMAT variable must be set.
(From OE-Core rev: 5d27db85d269f576929fd3c81f94e54d894cdf69)
Signed-off-by: Daniel Gomez <daniel@qtec.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These tmp paths end up in the test names making it hard to compare test runs
so filter them out, they're not useful for our purposes.
(From OE-Core rev: dc47b3855d03af962bab176c7aed9bd47426b419)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-Upgrade from lttng-ust_2.10.3.bb to lttng-ust_2.10.4.bb.
-lttng-ust/0001-compat-work-around-broken-_SC_NPROCESSORS_CONF-on-MU.patch
Removed since this is included in 2.10.4
(From OE-Core rev: dc25e9525495e00940da7716cbba6bca96423acd)
Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The git based recipe is for those who want to build lttng-modules with bleeding
edge kernel, to avoid regularly backporting patches from upstream.
Note that PREFERRED_VERSION needs to be set to select the git recipe instead of
the tar ball one.
(From OE-Core rev: 18dd8e719f7c845d7e4bb1148ef6adad80a9493e)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
