Skip to contentSkip to conversation

kernel: linux-yocto 3.14, linux-yocto-dev 3.16 and dependencies

PATCH In review Bruce Ashfield 6 participants 25 messages Jul 24, 2014 – Aug 12, 2014

lore
Share & tools
lore
#0 lore raw

cover kernel: linux-yocto 3.14, linux-yocto-dev 3.16 and dependencies

Richard/Saul,

Here are my consolidated changes for kernel updates.

For 3.14:

linux-yocto/3.14: vexpress and MVM firmware support
linux-yocto: x86_64: expand kernel stack to 16K linux-yocto/3.14: libata and generic CPU modalias handling

For linux-yocto-dev:

linux-yocto-dev: bump to v3.16+
lttng-modules: update to 2.5.0
kernel: don't copy .so.dbg files into kernel source install
kern-tools: adjust to full history meta-data

And for lttng on ARM:

lttng-modules: re-enable ARM builds

I've built and booted 3.16 on all the architectures, and also build my kernel-dev image type (which includes package that often break with kernel updates, and which I'll submit to oe-core separately). That's where the .so.db change for kernel.bbclass and the lttng update have come from.

Cheers,

Bruce

The following changes since commit 8b7116d25ed6255a03895d835e5a0560858ab496:

bitbake: Updated the the example 'bitbake -h' output to match the actual output, which has been recently patched to fix the '-S SIGNATURE_HANDLER, --dump-signatures=SIGNATURE_HANDLER' option. (2014-07-22 08:33:25 +0100)

are available in the git repository at:

git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (8):
linux-yocto/3.14: vexpress and MVM firmware support
lttng-modules: update to 2.5.0
linux-yocto: x86_64: expand kernel stack to 16K
linux-yocto-dev: bump to v3.16+
kernel: don't copy .so.dbg files into kernel source install
lttng-modules: re-enable ARM builds linux-yocto/3.14: libata and generic CPU modalias handling
kern-tools: adjust to full history meta-data

 meta/classes/kernel.bbclass                        |  2 +-
 .../kern-tools/kern-tools-native_git.bb            |  2 +-
 meta/recipes-kernel/linux/linux-yocto-dev.bb       |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb   |  6 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb |  4 +-
 meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 16 ++---
 ...compaction-instrumentation-to-3.16-kernel.patch | 83 ++++++++++++++++++++++
 ...ate-vmscan-instrumentation-to-3.16-kernel.patch | 70 ++++++++++++++++++
 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb   | 36 ----------
 ...tng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} | 10 +--
 10 files changed, 174 insertions(+), 57 deletions(-)
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.16-kernel.patch
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-vmscan-instrumentation-to-3.16-kernel.patch
 delete mode 100644 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb
 rename meta/recipes-kernel/lttng/{lttng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} (80%)
Signature · 1 line
1.8.1.2
#1 lore raw

PATCH 1/8 linux-yocto/3.14: vexpress and MVM firmware support

Updating the 3.14 SRCREVs to integrate the following changes:

meta: iwlwifi: Add MVM firmware support
vexpress: Pass LOADADDR to Makefile

---
 meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 16 ++++++++--------
 3 files changed, 13 insertions(+), 13 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb +3 -3
index 6d5096cd8565..61f9dbc9a14e 100644
@@ -3,9 +3,9 @@ require recipes-kernel/linux/linux-yocto.inc
 KBRANCH = "standard/preempt-rt/base"
 KBRANCH_qemuppc = "standard/preempt-rt/qemuppc"
 
-SRCREV_machine ?= "5c79217cdf1c16a3cacd28968e8c3e417e994c86"
-SRCREV_machine_qemuppc ?= "1ad208565754a1122df5500246f3142e2a3eff39"
-SRCREV_meta ?= "602be954ac45e8aea06cb93d6766bbf83c242090"
+SRCREV_machine ?= "568f018a22474939695a31709802bb8863c483d9"
+SRCREV_machine_qemuppc ?= "6af424a3a76a7fcf0cc7718b93f7a9db52383c25"
+SRCREV_meta ?= "b2af4e3528e65583c98f3a08c6edb0cad7a120b0"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
 
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb +2 -2
index 7eb90a6929a8..98381606ebb0 100644
@@ -8,8 +8,8 @@ LINUX_VERSION ?= "3.14.5"
 
 KMETA = "meta"
 
-SRCREV_machine ?= "96930820e0cb6d4b31d5e0c8f3174805f4a868b3"
-SRCREV_meta ?= "602be954ac45e8aea06cb93d6766bbf83c242090"
+SRCREV_machine ?= "686b9ddf58ea6b533be70fe9f4a6407557b263d2"
+SRCREV_meta ?= "b2af4e3528e65583c98f3a08c6edb0cad7a120b0"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
meta/recipes-kernel/linux/linux-yocto_3.14.bb +8 -8
index 1bdf520a9249..02909b79c029 100644
@@ -10,14 +10,14 @@ KBRANCH_qemux86  = "standard/common-pc/base"
 KBRANCH_qemux86-64  = "standard/common-pc-64/base"
 KBRANCH_qemumips64 = "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "2489f1f4d7aa27bf0808d7fa80a50399c643516d"
-SRCREV_machine_qemumips ?= "63b4ca3223d9481baa77f527f50d906d15747141"
-SRCREV_machine_qemuppc ?= "e5dfe8f89b45effe445d04e0f9b391948eb108ae"
-SRCREV_machine_qemux86 ?= "41d5fe27dc3d3e769cb6af01770cac3d75a91e1a"
-SRCREV_machine_qemux86-64 ?= "96930820e0cb6d4b31d5e0c8f3174805f4a868b3"
-SRCREV_machine_qemumips64 ?= "103df748c6e83d5874a8385592f758feeb818324"
-SRCREV_machine ?= "96930820e0cb6d4b31d5e0c8f3174805f4a868b3"
-SRCREV_meta ?= "602be954ac45e8aea06cb93d6766bbf83c242090"
+SRCREV_machine_qemuarm ?= "e3cbee86dcbc6c9b23a7cf69fe579da77c3836d1"
+SRCREV_machine_qemumips ?= "431de4758042fab2d62269574bb4ec3a783b43a0"
+SRCREV_machine_qemuppc ?= "1fc7009c9c8de594d75090b188c11a6ddd0d369e"
+SRCREV_machine_qemux86 ?= "116dacb5cebba538bc70e8056ebfa81d7ca6c061"
+SRCREV_machine_qemux86-64 ?= "686b9ddf58ea6b533be70fe9f4a6407557b263d2"
+SRCREV_machine_qemumips64 ?= "966c54ceb8cb797eafe987f9a16d306735057b42"
+SRCREV_machine ?= "686b9ddf58ea6b533be70fe9f4a6407557b263d2"
+SRCREV_meta ?= "b2af4e3528e65583c98f3a08c6edb0cad7a120b0"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
 
Signature · 1 line
1.8.1.2
#12 lore raw

PATCH 4/8 linux-yocto-dev: bump to v3.16+

In reply to Bruce Ashfield
---
 meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/linux/linux-yocto-dev.bb +1 -1
index 9b49eee87651..10f3d234ed25 100644
@@ -36,7 +36,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;bareclone=1;branch=${K
 SRCREV_machine ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
 SRCREV_meta ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
 
-LINUX_VERSION ?= "3.14+"
+LINUX_VERSION ?= "3.16+"
 LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
Signature · 1 line
1.8.1.2
#16 lore raw

PATCH 5/8 kernel: don't copy .so.dbg files into kernel source install

In reply to Bruce Ashfield

In 3.16+ x86-64 kernel builds produce a vdso64.so.dbg file. If this file is copied into the kernel source install multiple QA failures are triggered. Specifically, this file triggers a debug package split that results in files installed but not shipped, and invalid .debug file errors.

By ensuring that .so files are not copied, we avoid this incorrect split with no impact on future build phases.

---
 meta/classes/kernel.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/classes/kernel.bbclass +1 -1
index b2e9d4cb3631..128987303233 100644
@@ -232,7 +232,7 @@ kernel_do_install() {
 	# dir. This ensures the original Makefiles are used and not the
 	# redirecting Makefiles in the build directory.
 	#
-	find . -depth -not -name "*.cmd" -not -name "*.o" -not -path "./Documentation*" -not -path "./source*" -not -path "./.*" -print0 | cpio --null -pdlu $kerneldir
+	find . -depth -not -name "*.cmd" -not -name "*.o" -not -name "*.so.dbg" -not -path "./Documentation*" -not -path "./source*" -not -path "./.*" -print0 | cpio --null -pdlu $kerneldir
 	cp .config $kerneldir
 	if [ "${S}" != "${B}" ]; then
 		pwd="$PWD"
Signature · 1 line
1.8.1.2
#2 lore raw

PATCH 2/8 lttng-modules: update to 2.5.0

In reply to Bruce Ashfield

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.

---
 ...compaction-instrumentation-to-3.16-kernel.patch | 83 ++++++++++++++++++++++
 ...ate-vmscan-instrumentation-to-3.16-kernel.patch | 70 ++++++++++++++++++
 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb   | 36 ----------
 ...tng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} |  7 +-
 4 files changed, 157 insertions(+), 39 deletions(-)
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.16-kernel.patch
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-vmscan-instrumentation-to-3.16-kernel.patch
 delete mode 100644 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb
 rename meta/recipes-kernel/lttng/{lttng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} (85%)
meta/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.16-kernel.patch new file +83 -0
new file mode 100644
index 000000000000..0a056a947570
@@ -0,0 +1,83 @@
+From 0007344741ef65259bc52dea72259173dfbf96c0 Mon Sep 17 00:00:00 2001
+From: Mathieu Desnoyers <[email protected]>
+Date: Sun, 13 Jul 2014 13:33:21 -0400
+Subject: [PATCH 2/2] Update compaction instrumentation to 3.16 kernel
+
+Signed-off-by: Mathieu Desnoyers <[email protected]>
+---
+ instrumentation/events/lttng-module/compaction.h | 45 +++++++++++++++++++++++-
+ 1 file changed, 44 insertions(+), 1 deletion(-)
+
+diff --git a/instrumentation/events/lttng-module/compaction.h b/instrumentation/events/lttng-module/compaction.h
+index 1b237fa45ab0..22024e9ee582 100644
+--- a/instrumentation/events/lttng-module/compaction.h
++++ b/instrumentation/events/lttng-module/compaction.h
+@@ -6,6 +6,7 @@
+ 
+ #include <linux/types.h>
+ #include <linux/tracepoint.h>
++#include <linux/version.h>
+ #include <trace/events/gfpflags.h>
+ 
+ DECLARE_EVENT_CLASS(mm_compaction_isolate_template,
+@@ -45,6 +46,48 @@ DEFINE_EVENT(mm_compaction_isolate_template, mm_compaction_isolate_freepages,
+ 	TP_ARGS(nr_scanned, nr_taken)
+ )
+ 
++#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,16,0))
++TRACE_EVENT(mm_compaction_migratepages,
++
++	TP_PROTO(unsigned long nr_all,
++		int migrate_rc,
++		struct list_head *migratepages),
++
++	TP_ARGS(nr_all, migrate_rc, migratepages),
++
++	TP_STRUCT__entry(
++		__field(unsigned long, nr_migrated)
++		__field(unsigned long, nr_failed)
++	),
++
++	TP_fast_assign(
++		tp_assign(nr_migrated,
++			nr_all -
++			(migrate_rc >= 0 ? migrate_rc :
++				({
++					unsigned long nr_failed = 0;
++					struct list_head *page_lru;
++
++					list_for_each(page_lru, migratepages)
++						nr_failed++;
++					nr_failed;
++				})))
++		tp_assign(nr_failed,
++				({
++					unsigned long nr_failed = 0;
++					struct list_head *page_lru;
++
++					list_for_each(page_lru, migratepages)
++						nr_failed++;
++					nr_failed;
++				}))
++	),
++
++	TP_printk("nr_migrated=%lu nr_failed=%lu",
++		__entry->nr_migrated,
++		__entry->nr_failed)
++)
++#else /* #if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,16,0)) */
+ TRACE_EVENT(mm_compaction_migratepages,
+ 
+ 	TP_PROTO(unsigned long nr_migrated,
+@@ -66,7 +109,7 @@ TRACE_EVENT(mm_compaction_migratepages,
+ 		__entry->nr_migrated,
+ 		__entry->nr_failed)
+ )
+-
++#endif /* #else #if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,16,0)) */
+ 
+ #endif /* _TRACE_COMPACTION_H */
+ 
+-- 
+1.8.1.2
+
meta/recipes-kernel/lttng/lttng-modules/Update-vmscan-instrumentation-to-3.16-kernel.patch new file +70 -0

70 lines not on this page · raw message

meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb deleted +0 -36
deleted file mode 100644
index 81a3983c64f1..000000000000
@@ -1,36 +0,0 @@
-SECTION = "devel"
-SUMMARY = "Linux Trace Toolkit KERNEL MODULE"
-DESCRIPTION = "The lttng-modules 2.0 package contains the kernel tracer modules"
-LICENSE = "LGPLv2.1 & GPLv2"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=1412caf5a1aa90d6a48588a4794c0eac \
-                    file://gpl-2.0.txt;md5=751419260aa954499f7abaabaa882bbe \
-                    file://lgpl-2.1.txt;md5=243b725d71bb5df4a1e5920b344b86ad"
-
-DEPENDS = "virtual/kernel"
-
-inherit module
-
-SRCREV = "eef112db0e63feff6cbf0a98cda9af607cefb377"
-PV = "2.3.3"
-
-SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.3 \
-           file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
-           file://bio-bvec-iter.patch \
-          "
-
-export INSTALL_MOD_DIR="kernel/lttng-modules"
-export KERNEL_SRC="${STAGING_KERNEL_DIR}"
-
-
-S = "${WORKDIR}/git"
-
-do_install_append() {
-	# Delete empty directories to avoid QA failures if no modules were built
-	find ${D}/lib -depth -type d -empty -exec rmdir {} \;
-}
-
-python do_package_prepend() {
-    if not os.path.exists(os.path.join(d.getVar('D', True), 'lib/modules')):
-        bb.warn("%s: no modules were created; this may be due to CONFIG_TRACEPOINTS not being enabled in your kernel." % d.getVar('PN', True))
-}
-
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +4 -3
similarity index 85%
rename from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb
rename to meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
index 5e05ffc69853..5a99a5adae8b 100644
@@ -10,14 +10,15 @@ DEPENDS = "virtual/kernel"
 
 inherit module
 
-SRCREV = "a0383def517e3aebbbcebae61fe2bcfb50d31e71"
-PV = "2.4.1"
+SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
 # lttng currently blacklists arm with gcc-4.8
 COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
 
-SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.4 \
+SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
+           file://Update-compaction-instrumentation-to-3.16-kernel.patch \
+           file://Update-vmscan-instrumentation-to-3.16-kernel.patch \
            "
 
 export INSTALL_MOD_DIR="kernel/lttng-modules"
Signature · 1 line
1.8.1.2
#24 lore raw

PATCH 8/8 kern-tools: adjust to full history meta-data

In reply to Bruce Ashfield

In order to generate and support kernel trees with full history, we need to modify the kernel tools

e914d570232a kgit-checkpoint: ensure that full meta-data artifacts are maintained 192be836d318 kgit-scc: allow meta-data history to be maintained

---
 meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/kern-tools/kern-tools-native_git.bb +1 -1
index 1a2f881c7abf..24263e5d2b7e 100644
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c
 
 DEPENDS = "git-native"
 
-SRCREV = "a42509b01ccfe5020a226b23d3a52c07b3fb2051"
+SRCREV = "e914d570232a5a6aa47b721dafbab4af4209d93c"
 PR = "r12"
 PV = "0.2+git${SRCPV}"
 
Signature · 1 line
1.8.1.2
#23 lore raw

PATCH 7/8 linux-yocto/3.14: libata and generic CPU modalias handling

In reply to Bruce Ashfield

Updating the 3.14 yocto kernel to incorporate the following fix and feature of interest.

5724bf17acbf x86: align x86 arch with generic CPU modalias handling 6b9a52451a78 cpu: add generic support for CPU feature based module
38367de316bb libata: support the ata host which implements a queue depth less than 32

[YOCTO: #6489]

---
 meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 14 +++++++-------
 3 files changed, 10 insertions(+), 10 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb +2 -2
index da84c787f0ec..77215f6a517e 100644
@@ -3,8 +3,8 @@ require recipes-kernel/linux/linux-yocto.inc
 KBRANCH = "standard/preempt-rt/base"
 KBRANCH_qemuppc = "standard/preempt-rt/qemuppc"
 
-SRCREV_machine ?= "a70496be11fee0166481b1917745496e7eed863f"
-SRCREV_machine_qemuppc ?= "e8684b6b9919daea3e87c1e28efec0b3f39a3da7"
+SRCREV_machine ?= "8ef1733b66a1646b85338a310f787e0057a6a4e9"
+SRCREV_machine_qemuppc ?= "3079c794c30b0de82bc87b19cf477d82405a9094"
 SRCREV_meta ?= "b2af4e3528e65583c98f3a08c6edb0cad7a120b0"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb +1 -1
index 3c116e4be0ad..e28054fc4cf4 100644
@@ -8,7 +8,7 @@ LINUX_VERSION ?= "3.14.5"
 
 KMETA = "meta"
 
-SRCREV_machine ?= "5bee7e1583d4f075ac5a96d121271b347b384fd7"
+SRCREV_machine ?= "5724bf17acbf54cf61003ab242448fd96d189384"
 SRCREV_meta ?= "b2af4e3528e65583c98f3a08c6edb0cad7a120b0"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.14.bb +7 -7
index 031d2e546185..7b8b65382775 100644
@@ -10,13 +10,13 @@ KBRANCH_qemux86  = "standard/common-pc/base"
 KBRANCH_qemux86-64  = "standard/common-pc-64/base"
 KBRANCH_qemumips64 = "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "ed834b297cd5d36b303d36119549b90789e2890e"
-SRCREV_machine_qemumips ?= "12eba41a9a3bb017dcb45e721f20d7e68903b1c3"
-SRCREV_machine_qemuppc ?= "e2dbfaf796b18b0b9918f194e2a4c9e9eded0c2c"
-SRCREV_machine_qemux86 ?= "e8eb08d85050a944582e974cd461f741191bd07c"
-SRCREV_machine_qemux86-64 ?= "5bee7e1583d4f075ac5a96d121271b347b384fd7"
-SRCREV_machine_qemumips64 ?= "4ecb96fcb1826a127d6afbf67b8e69cccd7ccc8e"
-SRCREV_machine ?= "5bee7e1583d4f075ac5a96d121271b347b384fd7"
+SRCREV_machine_qemuarm ?= "b38b84aebf889d84e65e81ac11122b977f0c5155"
+SRCREV_machine_qemumips ?= "c9d827207d8dfab330787659b2842485dbd36d77"
+SRCREV_machine_qemuppc ?= "58b7cb00580985410ba8491c61e80d2572552ed9"
+SRCREV_machine_qemux86 ?= "5b327970eb1dba02c65cb8330dc8f3049c4fa580"
+SRCREV_machine_qemux86-64 ?= "5724bf17acbf54cf61003ab242448fd96d189384"
+SRCREV_machine_qemumips64 ?= "34837892b66eaa034cd3e3d339cab0ea6f594511"
+SRCREV_machine ?= "5724bf17acbf54cf61003ab242448fd96d189384"
 SRCREV_meta ?= "b2af4e3528e65583c98f3a08c6edb0cad7a120b0"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
Signature · 1 line
1.8.1.2
#11 lore raw

PATCH 3/8 linux-yocto: x86_64: expand kernel stack to 16K

In reply to Bruce Ashfield

Updating to backport the following mainline commit:

[
x86_64: expand kernel stack to 16K

commit 6538b8ea886e472f4431db8ca1d60478f838d14b upstream

While I play inhouse patches with much memory pressure on qemu-kvm, 3.14 kernel was randomly crashed. The reason was kernel stack overflow.

When I investigated the problem, the callstack was a little bit deeper by involve with reclaim functions but not direct reclaim path.

....
]

---
 meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 14 +++++++-------
 3 files changed, 10 insertions(+), 10 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb +2 -2
index 61f9dbc9a14e..da84c787f0ec 100644
@@ -3,8 +3,8 @@ require recipes-kernel/linux/linux-yocto.inc
 KBRANCH = "standard/preempt-rt/base"
 KBRANCH_qemuppc = "standard/preempt-rt/qemuppc"
 
-SRCREV_machine ?= "568f018a22474939695a31709802bb8863c483d9"
-SRCREV_machine_qemuppc ?= "6af424a3a76a7fcf0cc7718b93f7a9db52383c25"
+SRCREV_machine ?= "a70496be11fee0166481b1917745496e7eed863f"
+SRCREV_machine_qemuppc ?= "e8684b6b9919daea3e87c1e28efec0b3f39a3da7"
 SRCREV_meta ?= "b2af4e3528e65583c98f3a08c6edb0cad7a120b0"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb +1 -1
index 98381606ebb0..3c116e4be0ad 100644
@@ -8,7 +8,7 @@ LINUX_VERSION ?= "3.14.5"
 
 KMETA = "meta"
 
-SRCREV_machine ?= "686b9ddf58ea6b533be70fe9f4a6407557b263d2"
+SRCREV_machine ?= "5bee7e1583d4f075ac5a96d121271b347b384fd7"
 SRCREV_meta ?= "b2af4e3528e65583c98f3a08c6edb0cad7a120b0"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.14.bb +7 -7
index 02909b79c029..031d2e546185 100644
@@ -10,13 +10,13 @@ KBRANCH_qemux86  = "standard/common-pc/base"
 KBRANCH_qemux86-64  = "standard/common-pc-64/base"
 KBRANCH_qemumips64 = "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "e3cbee86dcbc6c9b23a7cf69fe579da77c3836d1"
-SRCREV_machine_qemumips ?= "431de4758042fab2d62269574bb4ec3a783b43a0"
-SRCREV_machine_qemuppc ?= "1fc7009c9c8de594d75090b188c11a6ddd0d369e"
-SRCREV_machine_qemux86 ?= "116dacb5cebba538bc70e8056ebfa81d7ca6c061"
-SRCREV_machine_qemux86-64 ?= "686b9ddf58ea6b533be70fe9f4a6407557b263d2"
-SRCREV_machine_qemumips64 ?= "966c54ceb8cb797eafe987f9a16d306735057b42"
-SRCREV_machine ?= "686b9ddf58ea6b533be70fe9f4a6407557b263d2"
+SRCREV_machine_qemuarm ?= "ed834b297cd5d36b303d36119549b90789e2890e"
+SRCREV_machine_qemumips ?= "12eba41a9a3bb017dcb45e721f20d7e68903b1c3"
+SRCREV_machine_qemuppc ?= "e2dbfaf796b18b0b9918f194e2a4c9e9eded0c2c"
+SRCREV_machine_qemux86 ?= "e8eb08d85050a944582e974cd461f741191bd07c"
+SRCREV_machine_qemux86-64 ?= "5bee7e1583d4f075ac5a96d121271b347b384fd7"
+SRCREV_machine_qemumips64 ?= "4ecb96fcb1826a127d6afbf67b8e69cccd7ccc8e"
+SRCREV_machine ?= "5bee7e1583d4f075ac5a96d121271b347b384fd7"
 SRCREV_meta ?= "b2af4e3528e65583c98f3a08c6edb0cad7a120b0"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
Signature · 1 line
1.8.1.2
#17 lore raw

PATCH 6/8 lttng-modules: re-enable ARM builds

In reply to Bruce Ashfield

With lttng 2.4.2 and gcc 4.9, we can now enable lttng-modules for ARM.

---
 meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +1 -2
index 5a99a5adae8b..d87374163556 100644
@@ -12,8 +12,7 @@ inherit module
 
 SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
-# lttng currently blacklists arm with gcc-4.8
-COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
+COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips|arm).*-linux'
 
 SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
Signature · 1 line
1.8.1.2
#18 lore raw

Re: [PATCH 6/8] lttng-modules: re-enable ARM builds

Quoted 12 lines · Bruce Ashfield

With lttng 2.4.2 and gcc 4.9, we can now enable lttng-modules for ARM.

---
 meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +0 -0
index 5a99a5adae8b..d87374163556 100644

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb inherit module · line 15

Quoted 6 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +1 -2
@@ -12,8 +12,7 @@ inherit module
 
 SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
-# lttng currently blacklists arm with gcc-4.8
-COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
+COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips|arm).*-linux'

Please squash this to 2/8 otherwise there is no arm version between 2/8 and 6/8.

Quoted 10 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +0 -0
 SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
Signature · 7 lines
1.8.1.2

-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#19 lore raw

Re: [PATCH 6/8] lttng-modules: re-enable ARM builds

Quoted 14 lines · Martin Jansa
Quoted 13 lines · Bruce Ashfield

With lttng 2.4.2 and gcc 4.9, we can now enable lttng-modules for ARM.

---
 meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +0 -0
index 5a99a5adae8b..d87374163556 100644
@@ -12,8 +12,7 @@ inherit module
 
Quoted 8 lines

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb inherit module · line 15

Quoted 5 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +1 -2
 SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
-# lttng currently blacklists arm with gcc-4.8
-COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
+COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips|arm).*-linux'

Please squash this to 2/8 otherwise there is no arm version between 2/8 and 6/8.

I'd rather not, since they are separate activities. I updated to 2.5, and then enable
ARM. One isolated change per commit. Bisectability in a small series is one thing, but also is the isolation of changes.

Richard can squash on merge is he wants, but I'm going to leave it as is.

Bruce

Quoted 21 lines
Quoted 11 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +0 -1
 SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
--

1.8.1.2

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
Martin 'JaMa' Jansa jabber: [email protected]

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#13 lore raw

Re: [PATCH 4/8] linux-yocto-dev: bump to v3.16+

In reply to Bruce Ashfield
Quoted 11 lines · Bruce Ashfield
---
  meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/linux/linux-yocto-dev.bb +0 -0
index 9b49eee87651..10f3d234ed25 100644

meta/recipes-kernel/linux/linux-yocto-dev.bb SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;bareclone=1;branch=${K · line 42

Quoted 8 lines
meta/recipes-kernel/linux/linux-yocto-dev.bb +1 -1
@@ -36,7 +36,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;bareclone=1;branch=${K
  SRCREV_machine ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
  SRCREV_meta ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
 
-LINUX_VERSION ?= "3.14+"
+LINUX_VERSION ?= "3.16+"
  LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
  PV = "${LINUX_VERSION}+git${SRCPV}"
 

So far the Autobuilder has found 1 issue with this and the x32 build

https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/182/steps/BuildImages/logs/stdio

I will send more failures as I see them.

Sau!

#14 lore raw

Re: [PATCH 4/8] linux-yocto-dev: bump to v3.16+

Quoted 31 lines · Saul Wold
Quoted 23 lines · Bruce Ashfield
---
  meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/linux/linux-yocto-dev.bb +0 -0
index 9b49eee87651..10f3d234ed25 100644
@@ -36,7 +36,7 @@ SRC_URI =

"git://git.yoctoproject.org/linux-yocto-dev.git;bareclone=1;branch=${K
SRCREV_machine ?=
'${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
SRCREV_meta ?=
'${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'

meta/recipes-kernel/linux/linux-yocto-dev.bb SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;bareclone=1;branch=${K · line 41

Quoted 4 lines
meta/recipes-kernel/linux/linux-yocto-dev.bb +1 -1
-LINUX_VERSION ?= "3.14+"
+LINUX_VERSION ?= "3.16+"
  LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
  PV = "${LINUX_VERSION}+git${SRCPV}"

So far the Autobuilder has found 1 issue with this and the x32 build

Quoted 2 lines

https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/182/steps/BuildImages/logs/stdio

Adding Tom, Darren and Nitin .. since this is something they need to handle

Bruce

Quoted 5 lines

I will send more failures as I see them.

Sau!

#15 lore raw

Re: [PATCH 4/8] linux-yocto-dev: bump to v3.16+

Quoted 35 lines · Bruce Ashfield
Quoted 34 lines · Saul Wold
Quoted 24 lines · Bruce Ashfield
---
  meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/linux/linux-yocto-dev.bb +0 -0
index 9b49eee87651..10f3d234ed25 100644
@@ -36,7 +36,7 @@ SRC_URI =

"git://git.yoctoproject.org/linux-yocto-dev.git;bareclone=1;branch=${K
SRCREV_machine ?=
'${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
SRCREV_meta ?=
'${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'

meta/recipes-kernel/linux/linux-yocto-dev.bb SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;bareclone=1;branch=${K · line 41

Quoted 4 lines
meta/recipes-kernel/linux/linux-yocto-dev.bb +1 -1
-LINUX_VERSION ?= "3.14+"
+LINUX_VERSION ?= "3.16+"
  LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
  PV = "${LINUX_VERSION}+git${SRCPV}"

So far the Autobuilder has found 1 issue with this and the x32 build

Quoted 4 lines
Quoted 2 lines

https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/182/steps/BuildImages/logs/stdio

Adding Tom, Darren and Nitin .. since this is something they need to handle

I retract my overly quick analysis.

I dropped this by mistake in 3.14, and didn't make the same change in my master meta data repository .. hence it also dropped in 3.16. I've restored this in both
locations now.

Bruce

Quoted 15 lines

Bruce

Quoted 5 lines

I will send more failures as I see them.

Sau!

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#20 lore raw

Re: [PATCH 6/8] lttng-modules: re-enable ARM builds

In reply to Bruce Ashfield
Quoted 24 lines · Bruce Ashfield
Quoted 14 lines · Martin Jansa
Quoted 13 lines · Bruce Ashfield

With lttng 2.4.2 and gcc 4.9, we can now enable lttng-modules for ARM.

---
 meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +0 -0
index 5a99a5adae8b..d87374163556 100644
@@ -12,8 +12,7 @@ inherit module
 
Quoted 8 lines

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb inherit module · line 15

Quoted 5 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +1 -2
 SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
-# lttng currently blacklists arm with gcc-4.8
-COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
+COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips|arm).*-linux'

Please squash this to 2/8 otherwise there is no arm version between 2/8 and 6/8.

Quoted 4 lines

I'd rather not, since they are separate activities. I updated to 2.5, and then enable
ARM. One isolated change per commit. Bisectability in a small series is one thing, but also is the isolation of changes.

2/8 commit message says:

We also drop the older 2.3.3 lttng-modules, since it is no longer required to support ARM builds.

Which isn't true at that time and it means that these changes aren't separate activities.

To keep them separate, remove 2.3.3 in this commit, not in upgrade to 2.5.0. (or with more work involved, enable arm in 2.4* together with 2.3.3 removal as someone reported arm+2.4* also working now).

Quoted 31 lines

Richard can squash on merge is he wants, but I'm going to leave it as is.

Bruce

Quoted 21 lines
Quoted 11 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +0 -1
 SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
--

1.8.1.2

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
Martin 'JaMa' Jansa jabber: [email protected]

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#21 lore raw

Re: [PATCH 6/8] lttng-modules: re-enable ARM builds

Quoted 35 lines · Martin Jansa
Quoted 24 lines · Bruce Ashfield
Quoted 14 lines · Martin Jansa
Quoted 13 lines · Bruce Ashfield

With lttng 2.4.2 and gcc 4.9, we can now enable lttng-modules for ARM.

---
 meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +0 -0
index 5a99a5adae8b..d87374163556 100644
@@ -12,8 +12,7 @@ inherit module
 
Quoted 8 lines

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb inherit module · line 15

Quoted 5 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +1 -2
 SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
-# lttng currently blacklists arm with gcc-4.8
-COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
+COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips|arm).*-linux'

Please squash this to 2/8 otherwise there is no arm version between 2/8 and 6/8.

Quoted 4 lines

I'd rather not, since they are separate activities. I updated to 2.5, and then enable
ARM. One isolated change per commit. Bisectability in a small series is one thing, but also is the isolation of changes.

2/8 commit message says:

We also drop the older 2.3.3 lttng-modules, since it is no longer required to support ARM builds.

Quoted 6 lines

Which isn't true at that time and it means that these changes aren't separate activities.

To keep them separate, remove 2.3.3 in this commit, not in upgrade to 2.5.0. (or with more work involved, enable arm in 2.4* together with 2.3.3 removal as someone reported arm+2.4* also working now).

That'll work, but not on tap for me today. I've got a whole set of backed up change behind my 3.16 work.

If Richard or Saul care, won't object to any splitting or squashing they want to do.

Bruce

Quoted 35 lines
Quoted 29 lines

Richard can squash on merge is he wants, but I'm going to leave it as is.

Bruce

Quoted 12 lines
Quoted 11 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +0 -1
 SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
--

1.8.1.2

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Quoted 9 lines

--
Martin 'JaMa' Jansa jabber: [email protected]

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Quoted 3 lines

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

--
Martin 'JaMa' Jansa jabber: [email protected]

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#22 lore raw

Re: [PATCH 6/8] lttng-modules: re-enable ARM builds

Quoted 43 lines · Bruce Ashfield
Quoted 35 lines · Martin Jansa
Quoted 24 lines · Bruce Ashfield
Quoted 14 lines · Martin Jansa
Quoted 13 lines · Bruce Ashfield

With lttng 2.4.2 and gcc 4.9, we can now enable lttng-modules for ARM.

---
 meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +0 -0
index 5a99a5adae8b..d87374163556 100644
@@ -12,8 +12,7 @@ inherit module
 
Quoted 8 lines

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb inherit module · line 15

Quoted 5 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +1 -2
 SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
-# lttng currently blacklists arm with gcc-4.8
-COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
+COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips|arm).*-linux'

Please squash this to 2/8 otherwise there is no arm version between 2/8 and 6/8.

Quoted 4 lines

I'd rather not, since they are separate activities. I updated to 2.5, and then enable
ARM. One isolated change per commit. Bisectability in a small series is one thing, but also is the isolation of changes.

2/8 commit message says:

We also drop the older 2.3.3 lttng-modules, since it is no longer required to support ARM builds.

Quoted 6 lines

Which isn't true at that time and it means that these changes aren't separate activities.

To keep them separate, remove 2.3.3 in this commit, not in upgrade to 2.5.0. (or with more work involved, enable arm in 2.4* together with 2.3.3 removal as someone reported arm+2.4* also working now).

Quoted 5 lines

That'll work, but not on tap for me today. I've got a whole set of backed up change behind my 3.16 work.

If Richard or Saul care, won't object to any splitting or squashing they want to do.

And I of course hit send to soon. There was supposed to be a second sentence here.

".. before I can split and retest over the weekend".

*sigh*. Off to get a coffee.

Bruce

Quoted 44 lines

Bruce

Quoted 29 lines
Quoted 29 lines

Richard can squash on merge is he wants, but I'm going to leave it as is.

Bruce

Quoted 21 lines
Quoted 11 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb +0 -1
 SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
--

1.8.1.2

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
Martin 'JaMa' Jansa jabber: [email protected]

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Quoted 6 lines
Quoted 3 lines

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

--
Martin 'JaMa' Jansa jabber: [email protected]

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#3 lore raw

Re: [PATCH 2/8] lttng-modules: update to 2.5.0

In reply to Bruce Ashfield
Quoted 19 lines · Bruce Ashfield

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.

---
 ...compaction-instrumentation-to-3.16-kernel.patch | 83 ++++++++++++++++++++++
 ...ate-vmscan-instrumentation-to-3.16-kernel.patch | 70 ++++++++++++++++++
 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb   | 36 ----------
 ...tng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} |  7 +-
 4 files changed, 157 insertions(+), 39 deletions(-)
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.16-kernel.patch
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-vmscan-instrumentation-to-3.16-kernel.patch
 delete mode 100644 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb
 rename meta/recipes-kernel/lttng/{lttng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} (85%)

...

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb DEPENDS = "virtual/kernel"

Quoted 8 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +0 -0
similarity index 85%
rename from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb
rename to meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
index 5e05ffc69853..5a99a5adae8b 100644
@@ -10,14 +10,15 @@ DEPENDS = "virtual/kernel"

Is the LICENSE = "LGPLv2.1 & GPLv2" correct?

git/LICENSE says:

* MIT-style license

These files are licensed under an MIT-style license. See mit-license.txt for details.

lib/prio_heap/lttng_prio_heap.h
lib/prio_heap/lttng_prio_heap.c
lib/bitfield.h

Quoted 26 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +4 -3
 inherit module
 
-SRCREV = "a0383def517e3aebbbcebae61fe2bcfb50d31e71"
-PV = "2.4.1"
+SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
 # lttng currently blacklists arm with gcc-4.8
 COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
 
-SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.4 \
+SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
+           file://Update-compaction-instrumentation-to-3.16-kernel.patch \
+           file://Update-vmscan-instrumentation-to-3.16-kernel.patch \
            "
 
 export INSTALL_MOD_DIR="kernel/lttng-modules"
Signature · 7 lines
1.8.1.2

-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#4 lore raw

Re: [PATCH 2/8] lttng-modules: update to 2.5.0

Quoted 23 lines · Martin Jansa
Quoted 19 lines · Bruce Ashfield

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.

---
 ...compaction-instrumentation-to-3.16-kernel.patch | 83 ++++++++++++++++++++++
 ...ate-vmscan-instrumentation-to-3.16-kernel.patch | 70 ++++++++++++++++++
 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb   | 36 ----------
 ...tng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} |  7 +-
 4 files changed, 157 insertions(+), 39 deletions(-)
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.16-kernel.patch
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-vmscan-instrumentation-to-3.16-kernel.patch
 delete mode 100644 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb
 rename meta/recipes-kernel/lttng/{lttng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} (85%)

...

Quoted 10 lines

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb DEPENDS = "virtual/kernel"

Quoted 8 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +0 -0
similarity index 85%
rename from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb
rename to meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
index 5e05ffc69853..5a99a5adae8b 100644
@@ -10,14 +10,15 @@ DEPENDS = "virtual/kernel"

Is the LICENSE = "LGPLv2.1 & GPLv2" correct?

Let me double check. I was doing an update and test, and didn't notice if this had changed.

Even if it did change, and I'm just uprev'ing .. I'll fix it, since it being wrong
in the past doesn't give me a free pass to keep it wrong in an update :)

Cheers,

Bruce

Quoted 49 lines

git/LICENSE says:

* MIT-style license

These files are licensed under an MIT-style license. See mit-license.txt for details.

lib/prio_heap/lttng_prio_heap.h
lib/prio_heap/lttng_prio_heap.c
lib/bitfield.h

Quoted 21 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +4 -4
 inherit module
 
-SRCREV = "a0383def517e3aebbbcebae61fe2bcfb50d31e71"
-PV = "2.4.1"
+SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
 # lttng currently blacklists arm with gcc-4.8
 COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
 
-SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.4 \
+SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
+           file://Update-compaction-instrumentation-to-3.16-kernel.patch \
+           file://Update-vmscan-instrumentation-to-3.16-kernel.patch \
            "
 
 export INSTALL_MOD_DIR="kernel/lttng-modules"
--

1.8.1.2

Quoted 5 lines

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
Martin 'JaMa' Jansa jabber: [email protected]

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#5 lore raw

Re: [PATCH 2/8] lttng-modules: update to 2.5.0

Quoted 35 lines · Bruce Ashfield
Quoted 23 lines · Martin Jansa
Quoted 19 lines · Bruce Ashfield

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.

---
 ...compaction-instrumentation-to-3.16-kernel.patch | 83 ++++++++++++++++++++++
 ...ate-vmscan-instrumentation-to-3.16-kernel.patch | 70 ++++++++++++++++++
 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb   | 36 ----------
 ...tng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} |  7 +-
 4 files changed, 157 insertions(+), 39 deletions(-)
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.16-kernel.patch
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-vmscan-instrumentation-to-3.16-kernel.patch
 delete mode 100644 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb
 rename meta/recipes-kernel/lttng/{lttng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} (85%)

...

Quoted 10 lines

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb DEPENDS = "virtual/kernel"

Quoted 8 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +0 -0
similarity index 85%
rename from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb
rename to meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
index 5e05ffc69853..5a99a5adae8b 100644
@@ -10,14 +10,15 @@ DEPENDS = "virtual/kernel"

Is the LICENSE = "LGPLv2.1 & GPLv2" correct?

Quoted 6 lines

Let me double check. I was doing an update and test, and didn't notice if this had changed.

Even if it did change, and I'm just uprev'ing .. I'll fix it, since it being wrong
in the past doesn't give me a free pass to keep it wrong in an update :)

Too funny. There have been the three MIT licence files since 2011 .. so I agree that the recipe's summary is long. I'll tack a patch onto the end of the series and wait to hear from RP/Saul about anything else I may have broken.

Bruce

Quoted 60 lines

Cheers,

Bruce

Quoted 43 lines

git/LICENSE says:

* MIT-style license

These files are licensed under an MIT-style license. See mit-license.txt for details.

lib/prio_heap/lttng_prio_heap.h
lib/prio_heap/lttng_prio_heap.c
lib/bitfield.h

Quoted 21 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +4 -4
 inherit module
 
-SRCREV = "a0383def517e3aebbbcebae61fe2bcfb50d31e71"
-PV = "2.4.1"
+SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
 # lttng currently blacklists arm with gcc-4.8
 COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
 
-SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.4 \
+SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
+           file://Update-compaction-instrumentation-to-3.16-kernel.patch \
+           file://Update-vmscan-instrumentation-to-3.16-kernel.patch \
            "
 
 export INSTALL_MOD_DIR="kernel/lttng-modules"
--

1.8.1.2

Quoted 5 lines

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
Martin 'JaMa' Jansa jabber: [email protected]

Quoted 6 lines

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#6 lore raw

Re: [PATCH 2/8] lttng-modules: update to 2.5.0

Quoted 40 lines · Bruce Ashfield
Quoted 38 lines · Bruce Ashfield
Quoted 23 lines · Martin Jansa
Quoted 19 lines · Bruce Ashfield

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.

---
 ...compaction-instrumentation-to-3.16-kernel.patch | 83 ++++++++++++++++++++++
 ...ate-vmscan-instrumentation-to-3.16-kernel.patch | 70 ++++++++++++++++++
 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb   | 36 ----------
 ...tng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} |  7 +-
 4 files changed, 157 insertions(+), 39 deletions(-)
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.16-kernel.patch
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-vmscan-instrumentation-to-3.16-kernel.patch
 delete mode 100644 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb
 rename meta/recipes-kernel/lttng/{lttng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} (85%)

...

Quoted 10 lines

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb DEPENDS = "virtual/kernel"

Quoted 8 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +0 -0
similarity index 85%
rename from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb
rename to meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
index 5e05ffc69853..5a99a5adae8b 100644
@@ -10,14 +10,15 @@ DEPENDS = "virtual/kernel"

Is the LICENSE = "LGPLv2.1 & GPLv2" correct?

Let me double check. I was doing an update and test, and didn't notice if this had changed.

Quoted 7 lines
Quoted 3 lines

Even if it did change, and I'm just uprev'ing .. I'll fix it, since it being wrong
in the past doesn't give me a free pass to keep it wrong in an update :)

Too funny. There have been the three MIT licence files since 2011 .. so I agree that the recipe's summary is long. I'll tack a patch onto the end of the series and wait to hear from RP/Saul about anything else I may have broken.

Sorry I thought you're maintainer of lttng-*, it seems like Laurentiu is
+ Laurentiu
maintainers.inc:RECIPE_MAINTAINER_pn-lttng-modules = "Laurentiu Palcu <[email protected]>" maintainers.inc:RECIPE_MAINTAINER_pn-lttng-ust = "Laurentiu Palcu <[email protected]>"

The same LICENSE issue is in lttng-ust

git/LICENSE:
...
* MIT license :

Public header files are distributed under the MIT license. See mit-license.txt for details.
...

Quoted 68 lines

Bruce

Quoted 60 lines

Cheers,

Bruce

Quoted 43 lines

git/LICENSE says:

* MIT-style license

These files are licensed under an MIT-style license. See mit-license.txt for details.

lib/prio_heap/lttng_prio_heap.h
lib/prio_heap/lttng_prio_heap.c
lib/bitfield.h

Quoted 21 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +4 -4
 inherit module
 
-SRCREV = "a0383def517e3aebbbcebae61fe2bcfb50d31e71"
-PV = "2.4.1"
+SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
 # lttng currently blacklists arm with gcc-4.8
 COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
 
-SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.4 \
+SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
+           file://Update-compaction-instrumentation-to-3.16-kernel.patch \
+           file://Update-vmscan-instrumentation-to-3.16-kernel.patch \
            "
 
 export INSTALL_MOD_DIR="kernel/lttng-modules"
--

1.8.1.2

Quoted 5 lines

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
Martin 'JaMa' Jansa jabber: [email protected]

Quoted 6 lines

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#7 lore raw

Re: [PATCH 2/8] lttng-modules: update to 2.5.0

Quoted 45 lines · Martin Jansa
Quoted 44 lines · Bruce Ashfield
Quoted 41 lines · Bruce Ashfield
Quoted 23 lines · Martin Jansa
Quoted 19 lines · Bruce Ashfield

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.

---
 ...compaction-instrumentation-to-3.16-kernel.patch | 83 ++++++++++++++++++++++
 ...ate-vmscan-instrumentation-to-3.16-kernel.patch | 70 ++++++++++++++++++
 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb   | 36 ----------
 ...tng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} |  7 +-
 4 files changed, 157 insertions(+), 39 deletions(-)
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.16-kernel.patch
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-vmscan-instrumentation-to-3.16-kernel.patch
 delete mode 100644 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb
 rename meta/recipes-kernel/lttng/{lttng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} (85%)

...

Quoted 10 lines

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb DEPENDS = "virtual/kernel"

Quoted 8 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +0 -0
similarity index 85%
rename from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb
rename to meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
index 5e05ffc69853..5a99a5adae8b 100644
@@ -10,14 +10,15 @@ DEPENDS = "virtual/kernel"

Is the LICENSE = "LGPLv2.1 & GPLv2" correct?

Let me double check. I was doing an update and test, and didn't notice if this had changed.

Even if it did change, and I'm just uprev'ing .. I'll fix it, since it being wrong
in the past doesn't give me a free pass to keep it wrong in an update :)

Quoted 5 lines
Quoted 3 lines

Too funny. There have been the three MIT licence files since 2011 .. so I agree that the recipe's summary is long. I'll tack a patch onto the end of the series and wait to hear from RP/Saul about anything else I may have broken.

Sorry I thought you're maintainer of lttng-*, it seems like Laurentiu is

No worries. I just get caught in the blast when lttng blows up during kernel uprevs, and I fix the wreckage so I can send out my updates :)

If we don't hear from Laurentiu, I can still do the update, so I'll hold it as a separate patch here.

Cheers,

Bruce

Quoted 85 lines

+ Laurentiu
maintainers.inc:RECIPE_MAINTAINER_pn-lttng-modules = "Laurentiu Palcu <[email protected]>" maintainers.inc:RECIPE_MAINTAINER_pn-lttng-ust = "Laurentiu Palcu <[email protected]>"

The same LICENSE issue is in lttng-ust

git/LICENSE:
...
* MIT license :

Public header files are distributed under the MIT license. See mit-license.txt for details.
...

Quoted 65 lines

Bruce

Quoted 57 lines

Cheers,

Bruce

Quoted 43 lines

git/LICENSE says:

* MIT-style license

These files are licensed under an MIT-style license. See mit-license.txt for details.

lib/prio_heap/lttng_prio_heap.h
lib/prio_heap/lttng_prio_heap.c
lib/bitfield.h

Quoted 21 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +4 -4
 inherit module
 
-SRCREV = "a0383def517e3aebbbcebae61fe2bcfb50d31e71"
-PV = "2.4.1"
+SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
 # lttng currently blacklists arm with gcc-4.8
 COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
 
-SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.4 \
+SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
+           file://Update-compaction-instrumentation-to-3.16-kernel.patch \
+           file://Update-vmscan-instrumentation-to-3.16-kernel.patch \
            "
 
 export INSTALL_MOD_DIR="kernel/lttng-modules"
--

1.8.1.2

Quoted 5 lines

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
Martin 'JaMa' Jansa jabber: [email protected]

Quoted 6 lines

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Quoted 3 lines

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

Quoted 3 lines

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

--
Martin 'JaMa' Jansa jabber: [email protected]

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#8 lore raw

Re: [PATCH 2/8] lttng-modules: update to 2.5.0

Quoted 50 lines · Bruce Ashfield
Quoted 49 lines · Martin Jansa
Quoted 47 lines · Bruce Ashfield
Quoted 35 lines · Bruce Ashfield
Quoted 23 lines · Martin Jansa
Quoted 19 lines · Bruce Ashfield

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.

---
 ...compaction-instrumentation-to-3.16-kernel.patch | 83 ++++++++++++++++++++++
 ...ate-vmscan-instrumentation-to-3.16-kernel.patch | 70 ++++++++++++++++++
 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb   | 36 ----------
 ...tng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} |  7 +-
 4 files changed, 157 insertions(+), 39 deletions(-)
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.16-kernel.patch
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-vmscan-instrumentation-to-3.16-kernel.patch
 delete mode 100644 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb
 rename meta/recipes-kernel/lttng/{lttng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} (85%)

...

Quoted 10 lines

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb DEPENDS = "virtual/kernel"

Quoted 8 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +0 -0
similarity index 85%
rename from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb
rename to meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
index 5e05ffc69853..5a99a5adae8b 100644
@@ -10,14 +10,15 @@ DEPENDS = "virtual/kernel"

Is the LICENSE = "LGPLv2.1 & GPLv2" correct?

Quoted 6 lines

Let me double check. I was doing an update and test, and didn't notice if this had changed.

Even if it did change, and I'm just uprev'ing .. I'll fix it, since it being wrong
in the past doesn't give me a free pass to keep it wrong in an update :)

Too funny. There have been the three MIT licence files since 2011 .. so I agree that the recipe's summary is long. I'll tack a patch onto the end of the series and wait to hear from RP/Saul about anything else I may have broken.

Quoted 7 lines
Quoted 1 line

Sorry I thought you're maintainer of lttng-*, it seems like Laurentiu is

No worries. I just get caught in the blast when lttng blows up during kernel uprevs, and I fix the wreckage so I can send out my updates :)

If we don't hear from Laurentiu, I can still do the update, so I'll hold it as a separate patch here.

I'm having fun with email, this thread got split into several different folders. I've merged the series after seeing the nightly builds pass ok (nice work Bruce!) so I'll take any follow up patches to fix anything like the LICENSE fields.

Cheers,

Richard

#9 lore raw

Re: [PATCH 2/8] lttng-modules: update to 2.5.0

In reply to Bruce Ashfield
Quoted 50 lines · Bruce Ashfield
Quoted 49 lines · Martin Jansa
Quoted 47 lines · Bruce Ashfield
Quoted 35 lines · Bruce Ashfield
Quoted 23 lines · Martin Jansa
Quoted 19 lines · Bruce Ashfield

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.

---
 ...compaction-instrumentation-to-3.16-kernel.patch | 83 ++++++++++++++++++++++
 ...ate-vmscan-instrumentation-to-3.16-kernel.patch | 70 ++++++++++++++++++
 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb   | 36 ----------
 ...tng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} |  7 +-
 4 files changed, 157 insertions(+), 39 deletions(-)
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.16-kernel.patch
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-vmscan-instrumentation-to-3.16-kernel.patch
 delete mode 100644 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb
 rename meta/recipes-kernel/lttng/{lttng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} (85%)

...

Quoted 10 lines

meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb DEPENDS = "virtual/kernel"

Quoted 8 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +0 -0
similarity index 85%
rename from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb
rename to meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
index 5e05ffc69853..5a99a5adae8b 100644
@@ -10,14 +10,15 @@ DEPENDS = "virtual/kernel"

Is the LICENSE = "LGPLv2.1 & GPLv2" correct?

Quoted 6 lines

Let me double check. I was doing an update and test, and didn't notice if this had changed.

Even if it did change, and I'm just uprev'ing .. I'll fix it, since it being wrong
in the past doesn't give me a free pass to keep it wrong in an update :)

Too funny. There have been the three MIT licence files since 2011 .. so I agree that the recipe's summary is long. I'll tack a patch onto the end of the series and wait to hear from RP/Saul about anything else I may have broken.

Quoted 7 lines
Quoted 1 line

Sorry I thought you're maintainer of lttng-*, it seems like Laurentiu is

No worries. I just get caught in the blast when lttng blows up during kernel uprevs, and I fix the wreckage so I can send out my updates :)

If we don't hear from Laurentiu, I can still do the update, so I'll hold it as a separate patch here.

Ping!

Someone just sent patch to upgrade lttng-ust, so I've asked him for LICENSE fix as well.

Quoted 91 lines
Quoted 85 lines

+ Laurentiu
maintainers.inc:RECIPE_MAINTAINER_pn-lttng-modules = "Laurentiu Palcu <[email protected]>" maintainers.inc:RECIPE_MAINTAINER_pn-lttng-ust = "Laurentiu Palcu <[email protected]>"

The same LICENSE issue is in lttng-ust

git/LICENSE:
...
* MIT license :

Public header files are distributed under the MIT license. See mit-license.txt for details.
...

Quoted 65 lines

Bruce

Quoted 57 lines

Cheers,

Bruce

Quoted 43 lines

git/LICENSE says:

* MIT-style license

These files are licensed under an MIT-style license. See mit-license.txt for details.

lib/prio_heap/lttng_prio_heap.h
lib/prio_heap/lttng_prio_heap.c
lib/bitfield.h

Quoted 21 lines
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb +4 -4
 inherit module
 
-SRCREV = "a0383def517e3aebbbcebae61fe2bcfb50d31e71"
-PV = "2.4.1"
+SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
 
 # lttng currently blacklists arm with gcc-4.8
 COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
 
-SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.4 \
+SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
            file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
+           file://Update-compaction-instrumentation-to-3.16-kernel.patch \
+           file://Update-vmscan-instrumentation-to-3.16-kernel.patch \
            "
 
 export INSTALL_MOD_DIR="kernel/lttng-modules"
--

1.8.1.2

Quoted 5 lines

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
Martin 'JaMa' Jansa jabber: [email protected]

Quoted 6 lines

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Quoted 3 lines

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

Quoted 3 lines

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

--
Martin 'JaMa' Jansa jabber: [email protected]

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#10 lore raw

Re: [PATCH 2/8] lttng-modules: update to 2.5.0

Hi Martin,

Quoted 5 lines · Martin Jansa
Quoted 5 lines
Quoted 1 line

Sorry I thought you're maintainer of lttng-*, it seems like Laurentiu is

No worries. I just get caught in the blast when lttng blows up during kernel uprevs, and I fix the wreckage so I can send out my updates :)

Quoted 7 lines
Quoted 2 lines

If we don't hear from Laurentiu, I can still do the update, so I'll hold it as a separate patch here.

Ping!

Someone just sent patch to upgrade lttng-ust, so I've asked him for LICENSE fix as well.

It seems I missed your previous email... :/ My apologies.

Regarding lttng* recipes, as of a couple of months ago, RP is the maintainer:

RECIPE_MAINTAINER_pn-lttng-modules = "Richard Purdie <[email protected]>" RECIPE_MAINTAINER_pn-lttng-tools = "Richard Purdie <[email protected]>" RECIPE_MAINTAINER_pn-lttng-ust = "Richard Purdie <[email protected]>"

laurentiu