lttng-modules: Update revision to grab last bugfix releases
PATCH 1/2 lttng-modules: Update revision to grab last bugfix releases
This updates lttng-modules for 2.3.2 and also includes a bugfix imported from 3.4 kernel. The changes included are:
6c26b01 Blacklist Linux kernels 3.10+
b97d469 LTTng trace-clock: shrink kernel blacklist
7d40f8e Version 2.3.1
2aecb9b Blacklist kernels 3.10.13 and 3.11.2
4f1217f Version 2.3.2
92fff0c Import fix from LTSI: 3.4+ RT kernels use CONFIG_PREEMPT_RT_FULL 1874075 lttng-statedump-impl: Fix lttng_list_interrupts for empty implementation
--- meta/recipes-kernel/lttng/lttng-modules_git.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
meta/recipes-kernel/lttng/lttng-modules_git.bb +2 -2
@@ -10,8 +10,8 @@ DEPENDS = "virtual/kernel" inherit module -SRCREV = "78c8710bb8e6b7f6301d95afec0305f40fa063ad" -PV = "2.3.0+git${SRCPV}" +SRCREV = "18740750760fde894eac0cd4e3ef4d8c7c4ba8c3" +PV = "2.3.2+git${SRCPV}" SRC_URI = "git://git.lttng.org/lttng-modules.git \ file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch"
Signature · 1 line
1.8.4.rc3
PATCH 2/2 lttng-modules: Backport fixes to allow use with 3.12 kernels
The 2.3 lttng-modules has support up to 3.11 kernels and the upcoming 3.12 had some API changes which need adjustments. This has been done in the 2.4 development branch and this patch backports those.
--- ...dump-impl-Use-generic-hard-irqs-for-Linux.patch | 115 +++++++++++++++++++++ ...-kmem-instrumentation-3.12-kernel-support.patch | 83 +++++++++++++++ ...date-vmscan-instrumentation-to-Linux-3.12.patch | 44 ++++++++ ...date-btrfs-instrumentation-to-3.12-kernel.patch | 44 ++++++++ ...-Update-RCU-instrumentation-to-Linux-3.12.patch | 32 ++++++ meta/recipes-kernel/lttng/lttng-modules_git.bb | 7 ++ 6 files changed, 325 insertions(+) create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0001-lttng-statedump-impl-Use-generic-hard-irqs-for-Linux.patch create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0002-update-kmem-instrumentation-3.12-kernel-support.patch create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0003-Update-vmscan-instrumentation-to-Linux-3.12.patch create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0004-Update-btrfs-instrumentation-to-3.12-kernel.patch create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0005-Update-RCU-instrumentation-to-Linux-3.12.patch
meta/recipes-kernel/lttng/lttng-modules/0001-lttng-statedump-impl-Use-generic-hard-irqs-for-Linux.patch new file +115 -0
@@ -0,0 +1,115 @@ +From 1eba72d2cdc5ba4aeea271540b66ed5e1ccc8f65 Mon Sep 17 00:00:00 2001 +From: Mathieu Desnoyers <[email protected]> +Date: Mon, 28 Oct 2013 12:11:00 +0000 +Subject: [PATCH 1/5] lttng-statedump-impl: Use generic hard irqs for Linux >= + 3.12 +Organization: O.S. Systems Software LTDA. + +Quoting the original patch changelog from Otavio Salvador: + +> The Linux kernel 3.12 uses the generic hard irqs system for all +> architectures and dropped the GENERIC_HARDIRQ option, as can be seen +> at the commit quoted below: +> +> ,---- +> | commit 0244ad004a54e39308d495fee0a2e637f8b5c317 +> | Author: Martin Schwidefsky <[email protected]> +> | Date: Fri Aug 30 09:39:53 2013 +0200 +> | +> | Remove GENERIC_HARDIRQ config option +> | +> | After the last architecture switched to generic hard irqs the config +> | options HAVE_GENERIC_HARDIRQS & GENERIC_HARDIRQS and the related code +> | for !CONFIG_GENERIC_HARDIRQS can be removed. +> | +> | Signed-off-by: Martin Schwidefsky <[email protected]> +> `---- + +Introduce wrapper/irq.h to move the feature availability testing logic +into a specific wrapper header. It now tests if the kernel version is +>= 3.12 or if CONFIG_GENERIC_HARDIRQS is defined (for older kernels). +Introduce the lttng-specific CONFIG_LTTNG_HAS_LIST_IRQ to track +availability of this feature within LTTng. + +Upstream-Status: Backport [2.4] + +Reported-by: Philippe Mangaud <[email protected]> +Reported-by: Otavio Salvador <[email protected]> +Signed-off-by: Mathieu Desnoyers <[email protected]> +--- + lttng-statedump-impl.c | 5 +++-- + wrapper/irq.h | 38 ++++++++++++++++++++++++++++++++++++++ + 2 files changed, 41 insertions(+), 2 deletions(-) + create mode 100644 wrapper/irq.h + +diff --git a/lttng-statedump-impl.c b/lttng-statedump-impl.c +index b8f9d35..1269a3e 100755 +--- a/lttng-statedump-impl.c ++++ b/lttng-statedump-impl.c +@@ -51,8 +51,9 @@ + #include "wrapper/spinlock.h" + #include "wrapper/fdtable.h" + #include "wrapper/nsproxy.h" ++#include "wrapper/irq.h" + +-#ifdef CONFIG_GENERIC_HARDIRQS ++#ifdef CONFIG_LTTNG_HAS_LIST_IRQ + #include <linux/irq.h> + #endif + +@@ -244,7 +245,7 @@ int lttng_enumerate_vm_maps(struct lttng_session *session) + } + #endif + +-#ifdef CONFIG_GENERIC_HARDIRQS ++#ifdef CONFIG_LTTNG_HAS_LIST_IRQ + + #if (LINUX_VERSION_CODE < KERNEL_VERSION(2,6,39)) + #define irq_desc_get_chip(desc) get_irq_desc_chip(desc) +diff --git a/wrapper/irq.h b/wrapper/irq.h +new file mode 100644 +index 0000000..b6feb0c +--- /dev/null ++++ b/wrapper/irq.h +@@ -0,0 +1,38 @@ ++#ifndef _LTTNG_WRAPPER_IRQ_H ++#define _LTTNG_WRAPPER_IRQ_H ++ ++/* ++ * wrapper/irq.h ++ * ++ * wrapper around linux/irq.h. ++ * ++ * Copyright (C) 2013 Mathieu Desnoyers <[email protected]> ++ * ++ * This library is free software; you can redistribute it and/or ++ * modify it under the terms of the GNU Lesser General Public ++ * License as published by the Free Software Foundation; only ++ * version 2.1 of the License. ++ * ++ * This library is distributed in the hope that it will be useful, ++ * but WITHOUT ANY WARRANTY; without even the implied warranty of ++ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU ++ * Lesser General Public License for more details. ++ * ++ * You should have received a copy of the GNU Lesser General Public ++ * License along with this library; if not, write to the Free Software ++ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA ++ */ ++ ++#include <linux/version.h> ++ ++/* ++ * Starting from the 3.12 Linux kernel, all architectures use the ++ * generic hard irqs system. More details can be seen at commit ++ * 0244ad004a54e39308d495fee0a2e637f8b5c317 in the Linux kernel GIT. ++ */ ++#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,12,0) \ ++ || defined(CONFIG_GENERIC_HARDIRQS)) ++# define CONFIG_LTTNG_HAS_LIST_IRQ ++#endif ++ ++#endif /* _LTTNG_WRAPPER_IRQ_H */ +-- +1.8.4.rc3 +
meta/recipes-kernel/lttng/lttng-modules/0002-update-kmem-instrumentation-3.12-kernel-support.patch new file +83 -0
83 lines not on this page · raw message
meta/recipes-kernel/lttng/lttng-modules/0003-Update-vmscan-instrumentation-to-Linux-3.12.patch new file +44 -0
44 lines not on this page · raw message
meta/recipes-kernel/lttng/lttng-modules/0004-Update-btrfs-instrumentation-to-3.12-kernel.patch new file +44 -0
44 lines not on this page · raw message
meta/recipes-kernel/lttng/lttng-modules/0005-Update-RCU-instrumentation-to-Linux-3.12.patch new file +32 -0
@@ -0,0 +1,32 @@ +From 5eb8705d39abd3d2668d3b118584039f70e39e5d Mon Sep 17 00:00:00 2001 +From: Mathieu Desnoyers <[email protected]> +Date: Thu, 31 Oct 2013 10:25:01 -0400 +Subject: [PATCH 5/5] Update RCU instrumentation to Linux 3.12 +Organization: O.S. Systems Software LTDA. + +Upstream-Status: Backport [2.4] + +Signed-off-by: Mathieu Desnoyers <[email protected]> +--- + instrumentation/events/lttng-module/rcu.h | 4 ++++ + 1 file changed, 4 insertions(+) + +diff --git a/instrumentation/events/lttng-module/rcu.h b/instrumentation/events/lttng-module/rcu.h +index ec541ba..1220fb7 100644 +--- a/instrumentation/events/lttng-module/rcu.h ++++ b/instrumentation/events/lttng-module/rcu.h +@@ -20,7 +20,11 @@ + */ + TRACE_EVENT(rcu_utilization, + ++#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,12,0)) ++ TP_PROTO(const char *s), ++#else /* #if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,12,0)) */ + TP_PROTO(char *s), ++#endif /* #else #if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,12,0)) */ + + TP_ARGS(s), + +-- +1.8.4.rc3 +
meta/recipes-kernel/lttng/lttng-modules_git.bb +7 -0
@@ -16,6 +16,13 @@ PV = "2.3.2+git${SRCPV}" SRC_URI = "git://git.lttng.org/lttng-modules.git \ file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch" +# Backport from 2.4 development branch +SRC_URI += "file://0001-lttng-statedump-impl-Use-generic-hard-irqs-for-Linux.patch \ + file://0002-update-kmem-instrumentation-3.12-kernel-support.patch \ + file://0003-Update-vmscan-instrumentation-to-Linux-3.12.patch \ + file://0004-Update-btrfs-instrumentation-to-3.12-kernel.patch \ + file://0005-Update-RCU-instrumentation-to-Linux-3.12.patch" + export INSTALL_MOD_DIR="kernel/lttng-modules" export KERNEL_SRC="${STAGING_KERNEL_DIR}"
Signature · 1 line
1.8.4.rc3
Quoted 11 lines · Otavio Salvador
This updates lttng-modules for 2.3.2 and also includes a bugfix imported from 3.4 kernel. The changes included are:
6c26b01 Blacklist Linux kernels 3.10+
b97d469 LTTng trace-clock: shrink kernel blacklist
7d40f8e Version 2.3.1
2aecb9b Blacklist kernels 3.10.13 and 3.11.2
4f1217f Version 2.3.2
92fff0c Import fix from LTSI: 3.4+ RT kernels useCONFIG_PREEMPT_RT_FULL1874075 lttng-statedump-impl: Fixlttng_list_interruptsfor empty implementation
Otavio,
Tried to build this locally and got the following failure with genericx86 and master:
| CC [M] /srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o | In file included from /srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-tracer.h:37:0, | from /srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.c:24: | /srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/wrapper/trace-clock.h:40:2: error: #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the timekeeping subsystem. Fixed by commit 7bd36014460f793c19e7d6c94dab67b0afcfcb7f \"timekeeping: Fix HRTICK related deadlock from ntp lock changes\" in Linux." | #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the timekeeping subsystem. Fixed by commit 7bd36014460f793c19e7d6c94dab67b0afcfcb7f \"timekeeping: Fix HRTICK related deadlock from ntp lock changes\" in Linux." | ^ | make[2]: *** [/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o] Error 1 | make[1]: *** [_module_/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git] Error 2 | make[1]: Leaving directory `/srv/ssd/sgw/builds/world/tmp/sysroots/genericx86/usr/src/kernel' | make: *** [default] Error 2 | ERROR: oe_runmake failed
So I am going to hold off on this patch set until you can resolve this.
Thanks
Sau!
Quoted 21 lines
Signed-off-by Otavio Salvador <[email protected]>--- meta/recipes-kernel/lttng/lttng-modules_git.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)meta/recipes-kernel/lttng/lttng-modules_git.bb +2
-2@@ -10,8 +10,8 @@ DEPENDS = "virtual/kernel" inherit module -SRCREV = "78c8710bb8e6b7f6301d95afec0305f40fa063ad" -PV = "2.3.0+git${SRCPV}" +SRCREV = "18740750760fde894eac0cd4e3ef4d8c7c4ba8c3" +PV = "2.3.2+git${SRCPV}" SRC_URI = "git://git.lttng.org/lttng-modules.git \ file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch"
Quoted 48 lines · Saul Wold
Quoted 4 lines · Otavio Salvador
This updates lttng-modules for 2.3.2 and also includes a bugfix imported from 3.4 kernel. The changes included are:
Quoted 9 lines
6c26b01 Blacklist Linux kernels 3.10+
b97d469 LTTng trace-clock: shrink kernel blacklist
7d40f8e Version 2.3.1
2aecb9b Blacklist kernels 3.10.13 and 3.11.2
4f1217f Version 2.3.2
92fff0c Import fix from LTSI: 3.4+ RT kernels useCONFIG_PREEMPT_RT_FULL1874075 lttng-statedump-impl: Fixlttng_list_interruptsfor empty implementationOtavio,
Tried to build this locally and got the following failure with genericx86 and master:
| CC [M]
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o| In file included from/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-tracer.h:37:0,
| from/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.c:24:
|/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/wrapper/trace-clock.h:40:2:
error: #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK related
deadlock from ntp lock changes\" in Linux."
| #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK related
deadlock from ntp lock changes\" in Linux."
| ^
| make[2]: *** [/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o] Error 1
| make[1]: *** [_module_/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git] Error 2
| make[1]: Leaving directory
`/srv/ssd/sgw/builds/world/tmp/sysroots/genericx86/usr/src/kernel'
| make: *** [default] Error 2
| ERROR:oe_runmakefailed
Quoted 1 line
So I am going to hold off on this patch set until you can resolve this.
Yes; this is becase the linux-yocto seems to not have been updated to
Quoted 1 line
3.10.13; so in fact it is failing to build to avoid people to
trigger the deadlock.
The change which introduces this in lttng-modules is:
http://git.lttng.org/?p=lttng-modules.git;a=commit;h=2aecb9b1cbb63f6c524ad9195d8fd06299ef9296
I can update this patch as 2.3.3 has been released and it includes the 3.12 fixes but please check when linux-yocto will be updated so we can fix it.
Regards,
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 55 lines · Otavio Salvador
Quoted 48 lines · Saul Wold
Quoted 4 lines · Otavio Salvador
This updates lttng-modules for 2.3.2 and also includes a bugfix imported from 3.4 kernel. The changes included are:
Quoted 9 lines
6c26b01 Blacklist Linux kernels 3.10+
b97d469 LTTng trace-clock: shrink kernel blacklist
7d40f8e Version 2.3.1
2aecb9b Blacklist kernels 3.10.13 and 3.11.2
4f1217f Version 2.3.2
92fff0c Import fix from LTSI: 3.4+ RT kernels useCONFIG_PREEMPT_RT_FULL1874075 lttng-statedump-impl: Fixlttng_list_interruptsfor empty implementationOtavio,
Tried to build this locally and got the following failure with genericx86 and master:
| CC [M]
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o| In file included from/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-tracer.h:37:0,
| from/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.c:24:
|/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/wrapper/trace-clock.h:40:2:
error: #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK related
deadlock from ntp lock changes\" in Linux."
| #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK related
deadlock from ntp lock changes\" in Linux."
| ^
| make[2]: *** [/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o] Error 1
| make[1]: *** [_module_/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git] Error 2
| make[1]: Leaving directory
`/srv/ssd/sgw/builds/world/tmp/sysroots/genericx86/usr/src/kernel'
| make: *** [default] Error 2
| ERROR:oe_runmakefailedQuoted 1 line
So I am going to hold off on this patch set until you can resolve this.
Yes; this is becase the linux-yocto seems to not have been updated to
Quoted 1 line
3.10.13; so in fact it is failing to build to avoid people to
trigger the deadlock.
Quoted 7 lines
The change which introduces this in lttng-modules is:
http://git.lttng.org/?p=lttng-modules.git;a=commit;h=2aecb9b1cbb63f6c524ad9195d8fd06299ef9296
I can update this patch as 2.3.3 has been released and it includes the 3.12 fixes but please check when linux-yocto will be updated so we can fix it.
Saul: What board are you building ? I've had linux-yocto on 3.10.17 for over a week
now.
The meta-yocto-bsps need a SRCREV bump, which I was just about to send out, but the code has been in tree for some time yet, and all the qemu* BSPs are already running at that revision.
Bruce
Quoted 12 lines
Regards,
--
Otavio SalvadorO.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
_______________________________________________
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"
Quoted 61 lines · Bruce Ashfield
Quoted 59 lines · Otavio Salvador
Quoted 48 lines · Saul Wold
Quoted 4 lines · Otavio Salvador
This updates lttng-modules for 2.3.2 and also includes a bugfix imported from 3.4 kernel. The changes included are:
Quoted 9 lines
6c26b01 Blacklist Linux kernels 3.10+
b97d469 LTTng trace-clock: shrink kernel blacklist
7d40f8e Version 2.3.1
2aecb9b Blacklist kernels 3.10.13 and 3.11.2
4f1217f Version 2.3.2
92fff0c Import fix from LTSI: 3.4+ RT kernels useCONFIG_PREEMPT_RT_FULL1874075 lttng-statedump-impl: Fixlttng_list_interruptsfor empty implementationOtavio,
Tried to build this locally and got the following failure with genericx86 and master:
| CC [M]
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o| In file included from/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-tracer.h:37:0,
| from/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.c:24:
|/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/wrapper/trace-clock.h:40:2:
error: #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK related
deadlock from ntp lock changes\" in Linux."
| #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK related
deadlock from ntp lock changes\" in Linux."
| ^
| make[2]: *** [/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o] Error 1
| make[1]: *** [_module_/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git] Error 2
| make[1]: Leaving directory
`/srv/ssd/sgw/builds/world/tmp/sysroots/genericx86/usr/src/kernel'
| make: *** [default] Error 2
| ERROR:oe_runmakefailedQuoted 1 line
So I am going to hold off on this patch set until you can resolve this.
Yes; this is becase the linux-yocto seems to not have been updated to
Quoted 1 line
3.10.13; so in fact it is failing to build to avoid people to
trigger the deadlock.
The change which introduces this in lttng-modules is:
http://git.lttng.org/?p=lttng-modules.git;a=commit;h=2aecb9b1cbb63f6c524ad9195d8fd06299ef9296
Quoted 7 lines
Quoted 3 lines
I can update this patch as 2.3.3 has been released and it includes the 3.12 fixes but please check when linux-yocto will be updated so we can fix it.
Saul: What board are you building ? I've had linux-yocto on 3.10.17 for over a week
now.
As mentioned above this is for genericx86, so maybe not all the BSPs are updated yet.
Sau!
Quoted 22 lines
The meta-yocto-bsps need a SRCREV bump, which I was just about to send out, but the code has been in tree for some time yet, and all the qemu* BSPs are already running at that revision.
Bruce
Quoted 12 lines
Regards,
--
Otavio SalvadorO.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 85 lines · Saul Wold
Quoted 84 lines · Bruce Ashfield
Quoted 79 lines · Otavio Salvador
Quoted 53 lines · Saul Wold
Quoted 5 lines · Otavio Salvador
This updates lttng-modules for 2.3.2 and also includes a bugfix imported from 3.4 kernel. The changes included are:
Quoted 10 lines
6c26b01 Blacklist Linux kernels 3.10+
b97d469 LTTng trace-clock: shrink kernel blacklist 7d40f8e Version 2.3.1
2aecb9b Blacklist kernels 3.10.13 and 3.11.2
4f1217f Version 2.3.2
92fff0c Import fix from LTSI: 3.4+ RT kernels useCONFIG_PREEMPT_RT_FULL
1874075 lttng-statedump-impl: Fixlttng_list_interruptsfor empty implementationOtavio,
Tried to build this locally and got the following failure with genericx86
and master:| CC [M]
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o| In file included from
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-tracer.h:37:0,
| from
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.c:24:
|
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/wrapper/trace-clock.h:40:2:
error: #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK
related
deadlock from ntp lock changes\" in Linux."
| #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK
related
deadlock from ntp lock changes\" in Linux."
| ^
| make[2]: ***[
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o] Error 1
| make[1]: ***Quoted 8 lines
[_module_/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git] Error 2
| make[1]: Leaving directory
`/srv/ssd/sgw/builds/world/tmp/sysroots/genericx86/usr/src/kernel'
| make: *** [default] Error 2
| ERROR:oe_runmakefailedSo I am going to hold off on this patch set until you can resolve this.
Yes; this is becase the linux-yocto seems to not have been updated to
Quoted 2 lines
3.10.13; so in fact it is failing to build to avoid people to
trigger the deadlock.
The change which introduces this in lttng-modules is:
http://git.lttng.org/?p=lttng-modules.git;a=commit;h=2aecb9b1cbb63f6c524ad9195d8fd06299ef9296
I can update this patch as 2.3.3 has been released and it includes the 3.12 fixes but please check when linux-yocto will be updated so we can fix it.
Quoted 7 lines
Quoted 3 lines
Saul: What board are you building ? I've had linux-yocto on 3.10.17 for over a week
now.As mentioned above this is for genericx86, so maybe not all the BSPs are updated yet.
Buried in the context, sorry about missing that.
Yes, I'm about to update the reference boards, but there's a install error that I'm fixing first, but I'll have the series out by end of day.
Bruce
Quoted 28 lines
Sau!
Quoted 23 lines
The meta-yocto-bsps need a SRCREV bump, which I was just about to send out, but the code has been in tree for some time yet, and all the qemu* BSPs are already running at that revision.
Bruce
Quoted 12 lines
Regards,
--
Otavio SalvadorO.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
_______________________________________________
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"
Quoted 91 lines · Bruce Ashfield
Quoted 90 lines · Saul Wold
Quoted 87 lines · Bruce Ashfield
Quoted 71 lines · Otavio Salvador
Quoted 53 lines · Saul Wold
Quoted 5 lines · Otavio Salvador
This updates lttng-modules for 2.3.2 and also includes a bugfix imported from 3.4 kernel. The changes included are:
Quoted 10 lines
6c26b01 Blacklist Linux kernels 3.10+
b97d469 LTTng trace-clock: shrink kernel blacklist 7d40f8e Version 2.3.1
2aecb9b Blacklist kernels 3.10.13 and 3.11.2
4f1217f Version 2.3.2
92fff0c Import fix from LTSI: 3.4+ RT kernels useCONFIG_PREEMPT_RT_FULL
1874075 lttng-statedump-impl: Fixlttng_list_interruptsfor empty implementationOtavio,
Tried to build this locally and got the following failure with genericx86
and master:| CC [M]
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o| In file included from
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-tracer.h:37:0,
| from
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.c:24:
|
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/wrapper/trace-clock.h:40:2:
error: #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK
related
deadlock from ntp lock changes\" in Linux."
| #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK
related
deadlock from ntp lock changes\" in Linux."
| ^
| make[2]: ***[
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o] Error 1
| make[1]: ***Quoted 8 lines
[_module_/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git] Error 2
| make[1]: Leaving directory
`/srv/ssd/sgw/builds/world/tmp/sysroots/genericx86/usr/src/kernel'
| make: *** [default] Error 2
| ERROR:oe_runmakefailedSo I am going to hold off on this patch set until you can resolve this.
Yes; this is becase the linux-yocto seems to not have been updated to
Quoted 2 lines
3.10.13; so in fact it is failing to build to avoid people to
trigger the deadlock.
Quoted 8 lines
The change which introduces this in lttng-modules is:
http://git.lttng.org/?p=lttng-modules.git;a=commit;h=2aecb9b1cbb63f6c524ad9195d8fd06299ef9296
I can update this patch as 2.3.3 has been released and it includes the 3.12 fixes but please check when linux-yocto will be updated so we can fix it.
Saul: What board are you building ? I've had linux-yocto on 3.10.17 for over a week
now.
Quoted 7 lines
Quoted 2 lines
As mentioned above this is for genericx86, so maybe not all the BSPs are updated yet.
Buried in the context, sorry about missing that.
Yes, I'm about to update the reference boards, but there's a install error that I'm fixing first, but I'll have the series out by end of day.
I just sent the update for this (cc'd [email protected]), but I haven't seen it loop around.
If you didn't get the patch, let me know and I'll try again.
Bruce
Quoted 37 lines
Bruce
Quoted 28 lines
Sau!
Quoted 23 lines
The meta-yocto-bsps need a SRCREV bump, which I was just about to send out, but the code has been in tree for some time yet, and all the qemu* BSPs are already running at that revision.
Bruce
Quoted 12 lines
Regards,
--
Otavio SalvadorO.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
_______________________________________________
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"
Quoted 98 lines · Bruce Ashfield
Quoted 96 lines · Bruce Ashfield
Quoted 85 lines · Saul Wold
Quoted 84 lines · Bruce Ashfield
Quoted 79 lines · Otavio Salvador
Quoted 53 lines · Saul Wold
Quoted 5 lines · Otavio Salvador
This updates lttng-modules for 2.3.2 and also includes a bugfix imported from 3.4 kernel. The changes included are:
Quoted 10 lines
6c26b01 Blacklist Linux kernels 3.10+
b97d469 LTTng trace-clock: shrink kernel blacklist 7d40f8e Version 2.3.1
2aecb9b Blacklist kernels 3.10.13 and 3.11.2
4f1217f Version 2.3.2
92fff0c Import fix from LTSI: 3.4+ RT kernels useCONFIG_PREEMPT_RT_FULL
1874075 lttng-statedump-impl: Fixlttng_list_interruptsfor empty implementationOtavio,
Tried to build this locally and got the following failure with genericx86
and master:| CC [M]
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o| In file included from
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-tracer.h:37:0,
| from
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.c:24:
|
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/wrapper/trace-clock.h:40:2:
error: #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK
related
deadlock from ntp lock changes\" in Linux."
| #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK
related
deadlock from ntp lock changes\" in Linux."
| ^
| make[2]: ***[
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o] Error 1
| make[1]: ***Quoted 8 lines
[_module_/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git] Error 2
| make[1]: Leaving directory
`/srv/ssd/sgw/builds/world/tmp/sysroots/genericx86/usr/src/kernel'
| make: *** [default] Error 2
| ERROR:oe_runmakefailedSo I am going to hold off on this patch set until you can resolve this.
Yes; this is becase the linux-yocto seems to not have been updated to
Quoted 2 lines
3.10.13; so in fact it is failing to build to avoid people to
trigger the deadlock.
The change which introduces this in lttng-modules is:
http://git.lttng.org/?p=lttng-modules.git;a=commit;h=2aecb9b1cbb63f6c524ad9195d8fd06299ef9296
I can update this patch as 2.3.3 has been released and it includes the 3.12 fixes but please check when linux-yocto will be updated so we can fix it.
Quoted 7 lines
Quoted 3 lines
Saul: What board are you building ? I've had linux-yocto on 3.10.17 for over a week
now.As mentioned above this is for genericx86, so maybe not all the BSPs are updated yet.
Buried in the context, sorry about missing that.
Quoted 7 lines
Quoted 2 lines
Yes, I'm about to update the reference boards, but there's a install error that I'm fixing first, but I'll have the series out by end of day.
I just sent the update for this (cc'd [email protected]), but I haven't seen it loop around.
If you didn't get the patch, let me know and I'll try again.
I have sent the new patch version.
It does the update to the 2.3.3 which include all the previous backported patches.
This should be considered for Dora as well as it fixes the deadlock and building with 3.12 kernels.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 108 lines · Otavio Salvador
Quoted 98 lines · Bruce Ashfield
Quoted 96 lines · Bruce Ashfield
Quoted 85 lines · Saul Wold
Quoted 84 lines · Bruce Ashfield
Quoted 79 lines · Otavio Salvador
Quoted 53 lines · Saul Wold
Quoted 5 lines · Otavio Salvador
This updates lttng-modules for 2.3.2 and also includes a bugfix imported from 3.4 kernel. The changes included are:
Quoted 10 lines
6c26b01 Blacklist Linux kernels 3.10+
b97d469 LTTng trace-clock: shrink kernel blacklist 7d40f8e Version 2.3.1
2aecb9b Blacklist kernels 3.10.13 and 3.11.2
4f1217f Version 2.3.2
92fff0c Import fix from LTSI: 3.4+ RT kernels useCONFIG_PREEMPT_RT_FULL
1874075 lttng-statedump-impl: Fixlttng_list_interruptsfor empty implementationOtavio,
Tried to build this locally and got the following failure with genericx86
and master:| CC [M]
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o| In file included from
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-tracer.h:37:0,
| from
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.c:24:
|
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/wrapper/trace-clock.h:40:2:
error: #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK
related
deadlock from ntp lock changes\" in Linux."
| #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK
related
deadlock from ntp lock changes\" in Linux."
| ^
| make[2]: ***[
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o] Error 1
| make[1]: ***Quoted 8 lines
[_module_/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git] Error 2
| make[1]: Leaving directory
`/srv/ssd/sgw/builds/world/tmp/sysroots/genericx86/usr/src/kernel'
| make: *** [default] Error 2
| ERROR:oe_runmakefailedSo I am going to hold off on this patch set until you can resolve this.
Yes; this is becase the linux-yocto seems to not have been updated to
Quoted 2 lines
3.10.13; so in fact it is failing to build to avoid people to
trigger the deadlock.
The change which introduces this in lttng-modules is:
http://git.lttng.org/?p=lttng-modules.git;a=commit;h=2aecb9b1cbb63f6c524ad9195d8fd06299ef9296
I can update this patch as 2.3.3 has been released and it includes the 3.12 fixes but please check when linux-yocto will be updated so we can fix it.
Quoted 7 lines
Quoted 3 lines
Saul: What board are you building ? I've had linux-yocto on 3.10.17 for over a week
now.As mentioned above this is for genericx86, so maybe not all the BSPs are updated yet.
Buried in the context, sorry about missing that.
Quoted 7 lines
Quoted 2 lines
Yes, I'm about to update the reference boards, but there's a install error that I'm fixing first, but I'll have the series out by end of day.
I just sent the update for this (cc'd [email protected]), but I haven't seen it loop around.
If you didn't get the patch, let me know and I'll try again.
Quoted 8 lines
I have sent the new patch version.
It does the update to the 2.3.3 which include all the previous backported patches.
This should be considered for Dora as well as it fixes the deadlock and building with 3.12 kernels.
Hi Otavio, thanks for suggesting this for dora, but dora's kernel is 3.10.11, and this is an update for lttng-modules, I'm not sure whether dora needs this.
Add Saul in the CC list.
// Robert
Quoted 150 lines · Robert Yang
Quoted 138 lines · Otavio Salvador
Quoted 128 lines · Bruce Ashfield
Quoted 119 lines · Bruce Ashfield
Quoted 112 lines · Saul Wold
Quoted 104 lines · Bruce Ashfield
Quoted 90 lines · Otavio Salvador
Quoted 69 lines · Saul Wold
Quoted 6 lines · Otavio Salvador
This updates lttng-modules for 2.3.2 and also includes a bugfix imported from 3.4 kernel. The changes included are:
Quoted 10 lines
6c26b01 Blacklist Linux kernels 3.10+
b97d469 LTTng trace-clock: shrink kernel blacklist 7d40f8e Version 2.3.1
2aecb9b Blacklist kernels 3.10.13 and 3.11.2
4f1217f Version 2.3.2
92fff0c Import fix from LTSI: 3.4+ RT kernels useCONFIG_PREEMPT_RT_FULL
1874075 lttng-statedump-impl: Fixlttng_list_interruptsfor empty implementationOtavio,
Tried to build this locally and got the following failure with genericx86
and master:| CC [M]
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o| In file included from
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-tracer.h:37:0,
| from
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.c:24:
|
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/wrapper/trace-clock.h:40:2:
error: #error "Linux kernels 3.10 and 3.11 introduce a deadlock in
the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK
related
deadlock from ntp lock changes\" in Linux."
| #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the
timekeeping subsystem. Fixed by commit7bd36014460f793c19e7d6c94dab67b0afcfcb7f\"timekeeping: Fix HRTICK
related
deadlock from ntp lock changes\" in Linux."
| ^
| make[2]: ***[
/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o] Error 1
| make[1]: ***[_module_/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git] Error 2
| make[1]: Leaving directory
`/srv/ssd/sgw/builds/world/tmp/sysroots/genericx86/usr/src/kernel'
| make: *** [default] Error 2
| ERROR:oe_runmakefailedQuoted 2 lines
So I am going to hold off on this patch set until you can resolve this.
Yes; this is becase the linux-yocto seems to not have been updated to
Quoted 3 lines
3.10.13; so in fact it is failing to build to avoid people to
trigger the deadlock.
The change which introduces this in lttng-modules is:
Quoted 7 lines
http://git.lttng.org/?p=lttng-modules.git;a=commit;h=2aecb9b1cbb63f6c524ad9195d8fd06299ef9296
I can update this patch as 2.3.3 has been released and it includes the
3.12 fixes but please check when linux-yocto will be updated so we can
fix it.Quoted 3 lines
Saul: What board are you building ? I've had linux-yocto on 3.10.17 for over a week
now.Quoted 3 lines
As mentioned above this is for genericx86, so maybe not all the BSPs are
updated yet.Quoted 4 lines
Buried in the context, sorry about missing that.
Yes, I'm about to update the reference boards, but there's a install error that I'm fixing first, but I'll have the series out by end of day.
Quoted 5 lines
I just sent the update for this (cc'd [email protected]), but I haven't
seen it loop around.If you didn't get the patch, let me know and I'll try again.
Quoted 8 lines
I have sent the new patch version.
It does the update to the 2.3.3 which include all the previous backported patches.
This should be considered for Dora as well as it fixes the deadlock and building with 3.12 kernels.
Quoted 6 lines
Hi Otavio, thanks for suggesting this for dora, but dora's kernel is 3.10.11,
and this is an update for lttng-modules, I'm not sure whether dora needs this.Add Saul in the CC list.
I think Dora ought to get the new 3.10 kernel updates; this can go along side with it.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 11 lines · Otavio Salvador
Quoted 10 lines · Robert Yang
Quoted 4 lines
This should be considered for Dora as well as it fixes the deadlock and building with 3.12 kernels.
Hi Otavio, thanks for suggesting this for dora, but dora's kernel is 3.10.11,
and this is an update for lttng-modules, I'm not sure whether dora needs this.
Quoted 5 lines
Quoted 1 line
Add Saul in the CC list.
I think Dora ought to get the new 3.10 kernel updates; this can go along side with it.
Hi Otavio,
I'm sorry, but I'm not sure whether we need update dora's kernel from 3.10.11 to 3.10.17, since we seldom do the package update for a stable branch, let's wait for others' comments:-).
// Robert
Quoted 20 lines · Robert Yang
Quoted 12 lines · Otavio Salvador
Quoted 10 lines · Robert Yang
Quoted 4 lines
This should be considered for Dora as well as it fixes the deadlock and building with 3.12 kernels.
Hi Otavio, thanks for suggesting this for dora, but dora's kernel is 3.10.11,
and this is an update for lttng-modules, I'm not sure whether dora needs this.Quoted 5 lines
Quoted 1 line
Add Saul in the CC list.
I think Dora ought to get the new 3.10 kernel updates; this can go along side with it.
Quoted 7 lines
Hi Otavio,
I'm sorry, but I'm not sure whether we need update dora's kernel from 3.10.11
to 3.10.17, since we seldom do the package update for a stable branch, let's wait for others' comments:-).
This is correct, I do not think we will be updating the kernel for a stable branch.
Sau!
Quoted 7 lines
// Robert
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 27 lines · Saul Wold
Quoted 26 lines · Robert Yang
Quoted 14 lines · Otavio Salvador
Quoted 11 lines · Robert Yang
Quoted 5 lines
This should be considered for Dora as well as it fixes the deadlock and building with 3.12 kernels.
Hi Otavio, thanks for suggesting this for dora, but dora's kernel is 3.10.11,
and this is an update for lttng-modules, I'm not sure whether dora needs this.Quoted 6 lines
Quoted 1 line
Add Saul in the CC list.
I think Dora ought to get the new 3.10 kernel updates; this can go along side with it.
Hi Otavio,
Quoted 7 lines
Quoted 5 lines
I'm sorry, but I'm not sure whether we need update dora's kernel from 3.10.11
to 3.10.17, since we seldom do the package update for a stable branch, let's wait for others' comments:-).This is correct, I do not think we will be updating the kernel for a stable branch.
This is wrong. We should update to 3.10.17 as this is the LTS release, otherwise what is the point of us using a LTS at all?
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 33 lines · Otavio Salvador
Quoted 32 lines · Saul Wold
Quoted 31 lines · Robert Yang
Quoted 14 lines · Otavio Salvador
Quoted 11 lines · Robert Yang
Quoted 5 lines
This should be considered for Dora as well as it fixes the deadlock and building with 3.12 kernels.
Hi Otavio, thanks for suggesting this for dora, but dora's kernel is 3.10.11,
and this is an update for lttng-modules, I'm not sure whether dora needs this.Quoted 6 lines
Quoted 1 line
Add Saul in the CC list.
I think Dora ought to get the new 3.10 kernel updates; this can go along side with it.
Hi Otavio,
I'm sorry, but I'm not sure whether we need update dora's kernel from 3.10.11
to 3.10.17, since we seldom do the package update for a stable branch, let's wait for others' comments:-).
Quoted 5 lines
Quoted 2 lines
This is correct, I do not think we will be updating the kernel for a stable branch.
This is wrong. We should update to 3.10.17 as this is the LTS release, otherwise what is the point of us using a LTS at all?
Obviously I'll be maintaining the LTS release in master, but that maintenance gets a mix of bug fixes and features associated with the upstream maintenance + LTSI + BSP requirements.
I've sent patches for the sustained branches in the past, and can do it here as well. But to do it properly, there really needs to be a dedicated kernel repository, since things like the LTSI import and new BSP support will be mixed into the tree if a single 3.10 repo is used.
I'm willing to split the repo and do -stable korg release updates, but at some point there are only so many repositories and versions that should be maintained at one time. As to what that number is, I don't have a firm one in mind.
At a minimum, it would be safe for the dora maintenance branch to take my latest kernel -stable imports, but in the not to distant future, it would need a separate maintenance stream.
Cheers,
Bruce
Quoted 1 line
Hi Bruce,
Here is the log status of the kernel layer between dora and master (18 commits).
I wonder are there any serious problems that we must upgrade it ?
$ git log dora..master --abbrev-commit --pretty=oneline meta/recipes-kernel
9a9a597 lttng-tools: Fixes incorrect path of ptest cases
e1e1ee5 linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for Beagleboard 779dec9 linux-yocto-rt/3.10: fix ntp merge issue
89c986c linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for Beagleboard 8a03d59 sysvinit: adjust boot sequence and remove hack from udev e9ec153 linux-yocto/3.10: fix qemuarm boot and spurious mips build warning baf005b linux-yocto/3.10: common-pc: add missing dependencies for BRCMSMAC dd361f0 linux-yocto/3.8: add crystalforest bsp legacy block drivers configurations 1fe7bca linux-yocto/3.10: haswell-wc and crystalforest support a23c7e9 linux-yocto-3.10: bump to 3.10.17 and -rt11
3129619 lttng-tools: make ptest able to work on target
5e42796 recipes: Remove PR = r0 from all recipes
2570f13 perf: flag __SANE_USERSPACE_TYPES__ to include int-ll64.h for mips64 56cc2f2 linux-yocto/3.10: MinnowBoard support
db1d37a perf: flag __SANE_USERSPACE_TYPES__ to include int-ll64.h for powerpc64 cd414c0 kmod: Update to Rev 15 via git
e83640d kmod: Add patch to fix seperate build dir of ptest
0f431a3 kmod-native: use bswap to work on older Linux hosts
// Robert
Quoted 67 lines · Bruce Ashfield
Quoted 33 lines · Otavio Salvador
Quoted 32 lines · Saul Wold
Quoted 31 lines · Robert Yang
Quoted 14 lines · Otavio Salvador
Quoted 11 lines · Robert Yang
Quoted 5 lines
This should be considered for Dora as well as it fixes the deadlock and building with 3.12 kernels.
Hi Otavio, thanks for suggesting this for dora, but dora's kernel is 3.10.11,
and this is an update for lttng-modules, I'm not sure whether dora needs this.Quoted 6 lines
Quoted 1 line
Add Saul in the CC list.
I think Dora ought to get the new 3.10 kernel updates; this can go along side with it.
Hi Otavio,
I'm sorry, but I'm not sure whether we need update dora's kernel from 3.10.11
to 3.10.17, since we seldom do the package update for a stable branch, let's wait for others' comments:-).Quoted 5 lines
Quoted 2 lines
This is correct, I do not think we will be updating the kernel for a stable branch.
This is wrong. We should update to 3.10.17 as this is the LTS release, otherwise what is the point of us using a LTS at all?
Obviously I'll be maintaining the LTS release in master, but that maintenance gets a mix of bug fixes and features associated with the upstream maintenance + LTSI + BSP requirements.
I've sent patches for the sustained branches in the past, and can do it here as well. But to do it properly, there really needs to be a dedicated kernel repository, since things like the LTSI import and new BSP support will be mixed into the tree if a single 3.10 repo is used.
I'm willing to split the repo and do -stable korg release updates, but at some point there are only so many repositories and versions that should be maintained at one time. As to what that number is, I don't have a firm one in mind.
At a minimum, it would be safe for the dora maintenance branch to take my latest kernel -stable imports, but in the not to distant future, it would need a separate maintenance stream.
Cheers,
Bruce
Quoted 1 line
Quoted 8 lines · Robert Yang
Hi Bruce,
Here is the log status of the kernel layer between dora and master (18 commits).
I wonder are there any serious problems that we must upgrade it ?
Quoted 8 lines
$ git log dora..master --abbrev-commit --pretty=oneline meta/recipes-kernel9a9a597 lttng-tools: Fixes incorrect path of ptest cases e1e1ee5 linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for Beagleboard
779dec9 linux-yocto-rt/3.10: fix ntp merge issue 89c986c linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for Beagleboard
You definitely want these. They fix USB and ethernet on the beagle
Quoted 6 lines
8a03d59 sysvinit: adjust boot sequence and remove hack from udev e9ec153 linux-yocto/3.10: fix qemuarm boot and spurious mips build warning baf005b linux-yocto/3.10: common-pc: add missing dependencies for BRCMSMAC dd361f0 linux-yocto/3.8: add crystalforest bsp legacy block drivers configurations
1fe7bca linux-yocto/3.10: haswell-wc and crystalforest support
Don't worry about the "add support" here, they are benign to all other goards.
Quoted 1 line
a23c7e9 linux-yocto-3.10: bump to 3.10.17 and -rt11
And this is where we need to be for the lttng fixes.
The other updates are also safe, you can't really pick and chose. Just take all my SRCREV updates for 3.10 on master, since they are all bugfixes or minor meta-data tweaks so far.
Bruce
Quoted 96 lines
3129619 lttng-tools: make ptest able to work on target
5e42796 recipes: Remove PR = r0 from all recipes
2570f13 perf: flag__SANE_USERSPACE_TYPES__to includeint-ll64.hfor mips64 56cc2f2 linux-yocto/3.10: MinnowBoard support
db1d37a perf: flag__SANE_USERSPACE_TYPES__to includeint-ll64.hfor powerpc64
cd414c0 kmod: Update to Rev 15 via git
e83640d kmod: Add patch to fix seperate build dir of ptest 0f431a3 kmod-native: use bswap to work on older Linux hosts// Robert
Quoted 66 lines · Bruce Ashfield
Quoted 40 lines · Otavio Salvador
Quoted 38 lines · Saul Wold
Quoted 36 lines · Robert Yang
Quoted 17 lines · Otavio Salvador
Quoted 13 lines · Robert Yang
Quoted 6 lines
This should be considered for Dora as well as it fixes the deadlock and building with 3.12 kernels.
Hi Otavio, thanks for suggesting this for dora, but dora's kernel is 3.10.11,
and this is an update for lttng-modules, I'm not sure whether dora needs
this.Quoted 7 lines
Quoted 1 line
Add Saul in the CC list.
I think Dora ought to get the new 3.10 kernel updates; this can go along side with it.
Hi Otavio,
I'm sorry, but I'm not sure whether we need update dora's kernel from 3.10.11
to 3.10.17, since we seldom do the package update for a stable branch, let's wait for others' comments:-).Quoted 7 lines
Quoted 3 lines
This is correct, I do not think we will be updating the kernel for a stable
branch.This is wrong. We should update to 3.10.17 as this is the LTS release, otherwise what is the point of us using a LTS at all?
Obviously I'll be maintaining the LTS release in master, but that maintenance gets a mix of bug fixes and features associated with the upstream maintenance + LTSI + BSP requirements.
I've sent patches for the sustained branches in the past, and can do it here as well. But to do it properly, there really needs to be a dedicated kernel repository, since things like the LTSI import and new BSP support will be mixed into the tree if a single 3.10 repo is used.
I'm willing to split the repo and do -stable korg release updates, but at some point there are only so many repositories and versions that should be maintained at one time. As to what that number is, I don't have a firm one in mind.
Quoted 12 lines
At a minimum, it would be safe for the dora maintenance branch to take my latest kernel -stable imports, but in the not to distant future, it would need a separate maintenance stream.
Cheers,
Bruce
Quoted 1 line
_______________________________________________
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"
Hi Bruce,
Thanks, we are going to update the kernel from 3.10.11 to 3.10.17 for dora if there is no objections.
Will we use another kernel source repo for dora ? Or just cherry-pick these commits ?
// Robert
Quoted 138 lines · Bruce Ashfield
Quoted 8 lines · Robert Yang
Hi Bruce,
Here is the log status of the kernel layer between dora and master (18 commits).
I wonder are there any serious problems that we must upgrade it ?
Quoted 8 lines
$ git log dora..master --abbrev-commit --pretty=oneline meta/recipes-kernel9a9a597 lttng-tools: Fixes incorrect path of ptest cases e1e1ee5 linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for Beagleboard
779dec9 linux-yocto-rt/3.10: fix ntp merge issue 89c986c linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for BeagleboardYou definitely want these. They fix USB and ethernet on the beagle
Quoted 6 lines
8a03d59 sysvinit: adjust boot sequence and remove hack from udev e9ec153 linux-yocto/3.10: fix qemuarm boot and spurious mips build warning baf005b linux-yocto/3.10: common-pc: add missing dependencies for BRCMSMAC dd361f0 linux-yocto/3.8: add crystalforest bsp legacy block drivers configurations
1fe7bca linux-yocto/3.10: haswell-wc and crystalforest supportDon't worry about the "add support" here, they are benign to all other goards.
Quoted 1 line
a23c7e9 linux-yocto-3.10: bump to 3.10.17 and -rt11
And this is where we need to be for the lttng fixes.
The other updates are also safe, you can't really pick and chose. Just take all my SRCREV updates for 3.10 on master, since they are all bugfixes or minor meta-data tweaks so far.
Bruce
Quoted 96 lines
3129619 lttng-tools: make ptest able to work on target
5e42796 recipes: Remove PR = r0 from all recipes
2570f13 perf: flag__SANE_USERSPACE_TYPES__to includeint-ll64.hfor mips64 56cc2f2 linux-yocto/3.10: MinnowBoard support
db1d37a perf: flag__SANE_USERSPACE_TYPES__to includeint-ll64.hfor powerpc64
cd414c0 kmod: Update to Rev 15 via git
e83640d kmod: Add patch to fix seperate build dir of ptest 0f431a3 kmod-native: use bswap to work on older Linux hosts// Robert
Quoted 66 lines · Bruce Ashfield
Quoted 40 lines · Otavio Salvador
Quoted 38 lines · Saul Wold
Quoted 36 lines · Robert Yang
Quoted 17 lines · Otavio Salvador
Quoted 13 lines · Robert Yang
Quoted 6 lines
This should be considered for Dora as well as it fixes the deadlock and building with 3.12 kernels.
Hi Otavio, thanks for suggesting this for dora, but dora's kernel is 3.10.11,
and this is an update for lttng-modules, I'm not sure whether dora needs
this.Quoted 7 lines
Quoted 1 line
Add Saul in the CC list.
I think Dora ought to get the new 3.10 kernel updates; this can go along side with it.
Hi Otavio,
I'm sorry, but I'm not sure whether we need update dora's kernel from 3.10.11
to 3.10.17, since we seldom do the package update for a stable branch, let's wait for others' comments:-).Quoted 7 lines
Quoted 3 lines
This is correct, I do not think we will be updating the kernel for a stable
branch.This is wrong. We should update to 3.10.17 as this is the LTS release, otherwise what is the point of us using a LTS at all?
Obviously I'll be maintaining the LTS release in master, but that maintenance gets a mix of bug fixes and features associated with the upstream maintenance + LTSI + BSP requirements.
I've sent patches for the sustained branches in the past, and can do it here as well. But to do it properly, there really needs to be a dedicated kernel repository, since things like the LTSI import and new BSP support will be mixed into the tree if a single 3.10 repo is used.
I'm willing to split the repo and do -stable korg release updates, but at some point there are only so many repositories and versions that should be maintained at one time. As to what that number is, I don't have a firm one in mind.
Quoted 12 lines
At a minimum, it would be safe for the dora maintenance branch to take my latest kernel -stable imports, but in the not to distant future, it would need a separate maintenance stream.
Cheers,
Bruce
Quoted 1 line
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 8 lines · Robert Yang
Hi Bruce,
Thanks, we are going to update the kernel from 3.10.11 to 3.10.17 for dora if there is no objections.
Will we use another kernel source repo for dora ? Or just cherry-pick these commits ?
Just do the cherry picks. The repository is safe for the dora branch. If that changes
in the future, we can fork it into a new repo.
Cheers,
Bruce
Quoted 170 lines
// Robert
Quoted 164 lines · Bruce Ashfield
Quoted 12 lines · Robert Yang
Hi Bruce,
Here is the log status of the kernel layer between dora and master (18 commits).
I wonder are there any serious problems that we must upgrade it ?
$ git log dora..master --abbrev-commit --pretty=oneline meta/recipes-kernelQuoted 6 lines
9a9a597 lttng-tools: Fixes incorrect path of ptest cases e1e1ee5 linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for Beagleboard
779dec9 linux-yocto-rt/3.10: fix ntp merge issue 89c986c linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for BeagleboardYou definitely want these. They fix USB and ethernet on the beagle
Quoted 8 lines
8a03d59 sysvinit: adjust boot sequence and remove hack from udev e9ec153 linux-yocto/3.10: fix qemuarm boot and spurious mips build warning
baf005b linux-yocto/3.10: common-pc: add missing dependencies for BRCMSMAC
dd361f0 linux-yocto/3.8: add crystalforest bsp legacy block drivers configurations
1fe7bca linux-yocto/3.10: haswell-wc and crystalforest supportDon't worry about the "add support" here, they are benign to all other goards.
Quoted 1 line
a23c7e9 linux-yocto-3.10: bump to 3.10.17 and -rt11
And this is where we need to be for the lttng fixes.
The other updates are also safe, you can't really pick and chose. Just take all
my SRCREV updates for 3.10 on master, since they are all bugfixes or minor meta-data tweaks so far.Bruce
Quoted 110 lines
3129619 lttng-tools: make ptest able to work on target 5e42796 recipes: Remove PR = r0 from all recipes
2570f13 perf: flag__SANE_USERSPACE_TYPES__to includeint-ll64.hfor mips64
56cc2f2 linux-yocto/3.10: MinnowBoard support
db1d37a perf: flag__SANE_USERSPACE_TYPES__to includeint-ll64.hfor powerpc64
cd414c0 kmod: Update to Rev 15 via git
e83640d kmod: Add patch to fix seperate build dir of ptest 0f431a3 kmod-native: use bswap to work on older Linux hosts// Robert
Quoted 79 lines · Bruce Ashfield
Quoted 49 lines · Otavio Salvador
Quoted 46 lines · Saul Wold
Quoted 43 lines · Robert Yang
Quoted 21 lines · Otavio Salvador
Quoted 16 lines · Robert Yang
Quoted 8 lines
This should be considered for Dora as well as it fixes the deadlock
and building with 3.12 kernels.Hi Otavio, thanks for suggesting this for dora, but dora's kernel is
3.10.11,
and this is an update for lttng-modules, I'm not sure whether dora needs
this.Quoted 8 lines
Quoted 1 line
Add Saul in the CC list.
I think Dora ought to get the new 3.10 kernel updates; this can go along side with it.
Hi Otavio,
I'm sorry, but I'm not sure whether we need update dora's kernel from 3.10.11
to 3.10.17, since we seldom do the package update for a stable branch,
let's wait for others' comments:-).Quoted 8 lines
Quoted 3 lines
This is correct, I do not think we will be updating the kernel for a stable
branch.This is wrong. We should update to 3.10.17 as this is the LTS release, otherwise what is the point of us using a LTS at all?
Obviously I'll be maintaining the LTS release in master, but that maintenance gets a mix of bug fixes and features associated with the upstream maintenance + LTSI + BSP requirements.
I've sent patches for the sustained branches in the past, and can do it here as well. But to do it properly, there really needs to be a dedicated kernel repository, since things like the LTSI import and new BSP support will be mixed into the tree if a single 3.10 repo is used.
I'm willing to split the repo and do -stable korg release updates, but at some point there are only so many repositories and versions that should be maintained at one time. As to what that number is, I don't have
a firm one in mind.Quoted 12 lines
At a minimum, it would be safe for the dora maintenance branch to take my latest kernel -stable imports, but in the not to distant future, it would need a separate maintenance stream.
Cheers,
Bruce
Quoted 1 line
_______________________________________________
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"
Quoted 20 lines · On Monday 18 November 2013 07:31:16 Saul Wold wrote:
Quoted 19 lines · Robert Yang
Quoted 11 lines · Otavio Salvador
On Mon, Nov 18, 2013 at 10:25 AM, Robert Yang
Quoted 8 lines · <[email protected]> wrote:
Quoted 2 lines
This should be considered for Dora as well as it fixes the deadlock and building with 3.12 kernels.
Hi Otavio, thanks for suggesting this for dora, but dora's kernel is 3.10.11,
and this is an update for lttng-modules, I'm not sure whether dora needs this.Quoted 4 lines
Quoted 1 line
Add Saul in the CC list.
I think Dora ought to get the new 3.10 kernel updates; this can go along side with it.
Hi Otavio,
Quoted 7 lines
Quoted 4 lines
I'm sorry, but I'm not sure whether we need update dora's kernel from 3.10.11
to 3.10.17, since we seldom do the package update for a stable branch, let's wait for others' comments:-).This is correct, I do not think we will be updating the kernel for a stable branch.
FWIW, there is a precedent for this in dylan - I relied upon Bruce sending patches that he felt were appropriate for the branch, and he did that on at least one occasion.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre