linaro-kernel

linaro-kernel@lists.linaro.org

10095 discussions

Re: [LNG] [PATCH] linaro/configs: add hugepage support into linaro-base

by Kim Phillips

On Mon, 30 Sep 2013 12:00:36 -0700 Zi Shen Lim <zishen.lim(a)linaro.org> wrote: > On Mon, Sep 30, 2013 at 12:03 PM, Anders Roxell > <anders.roxell(a)linaro.org> wrote: > > Hi, > > > > On 2013-09-30 11:48, Zi Shen Lim wrote: > >> Signed-off-by: Zi Shen Lim <zishen.lim(a)linaro.org> > >> --- > >> linaro/configs/linaro-base.conf | 4 ++++ > >> 1 file changed, 4 insertions(+) > >> > >> diff --git a/linaro/configs/linaro-base.conf b/linaro/configs/linaro-base.conf > >> index 947ca1f..0093640 100644 > >> --- a/linaro/configs/linaro-base.conf > >> +++ b/linaro/configs/linaro-base.conf > >> @@ -92,3 +92,7 @@ CONFIG_HW_PERF_EVENTS=y > >> CONFIG_FUNCTION_TRACER=y > >> CONFIG_ENABLE_DEFAULT_TRACERS=y > >> CONFIG_PROC_DEVICETREE=y > >> +CONFIG_HUGETLB_PAGE=y > >> +CONFIG_HUGETLBFS=y > >> +CONFIG_TRANSPARENT_HUGEPAGE=y > >> +CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y > > This CONFIG_* fragments are already in linaro/configs/linaro-base64.conf > > right? > > > > Isn't linaro-base64.conf meant for ARMv8? > > We need hugepage support on existing 32-bit / ARMv7 platforms too, don't we? [adding linaro-kernel, Andrey] Yes, it seems the base64 component is a misnomer, at least for now. Meanwhile, if this patch is targeted to the main linaro kernel, please send via the linaro-kernel list, cc'ing linaro-networking. If not, then perhaps a separate .conf file is in order? Anyway, I think we'd all prefer a resolution within the main linaro kernel for hugepage support. > > and we are building with it in our ci/job/linux-lng* scripts... perhaps those should be patched as well. Kim

11 years, 9 months

linus/master boot: 29 pass, 0 fail (v3.12-rc3-65-gf927318)

by Kevin Hilman build bot

11 years, 9 months

linus/master boot: 29 pass, 0 fail (v3.12-rc3-59-g522d6d3)

by Kevin Hilman build bot

11 years, 9 months

linus/master boot: 29 pass, 0 fail (v3.12-rc3-36-gdf532d5)

by Kevin Hilman build bot

11 years, 9 months

linus/master boot: 29 pass, 2 fail (v3.12-rc3-14-g5c282e8)

by Kevin Hilman build bot

Automated DT boot report for various ARM defconfigs. Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo'). Tree/Branch: linus/master Git describe: v3.12-rc3-14-g5c282e8 Commit: 5c282e858f Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/egtvedt/linux-avr32 Failed boot tests (console logs at the end) =========================================== am335x-bone: FAIL: arm-omap2plus_defconfig armada-370-mirabox: FAIL: arm-mvebu_defconfig Full Report =========== arm-tegra_defconfig ------------------- tegra30-beaver PASS: 0 min 18.0 sec arm-omap2plus_defconfig ----------------------- am335x-boneblack PASS: 0 min 30.4 sec omap3-beagle-xm PASS: 1 min 24.1 sec omap4-panda-es PASS: 1 min 20.6 sec am335x-bone FAIL: 0 min 50.3 sec omap3-tobi,3530overo PASS: 0 min 42.4 sec omap4-panda PASS: 1 min 5.6 sec am335xbone PASS: 0 min 25.4 sec omap3-tobi,3730storm PASS: 0 min 41.2 sec omap3-beagle PASS: 1 min 0.2 sec arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.5 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.3 sec imx6q-wandboard PASS: 0 min 15.1 sec arm-multi_v7_defconfig ---------------------- tegra30-beaver PASS: 0 min 15.2 sec am335x-boneblack PASS: 0 min 34.7 sec omap3-beagle-xm PASS: 0 min 51.8 sec armada-370-mirabox PASS: 0 min 19.5 sec omap4-panda PASS: 0 min 58.5 sec omap4-panda-es PASS: 1 min 6.6 sec sun4i-a10-cubieboard PASS: 0 min 11.7 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.5 sec omap3-tobi,3530overo PASS: 0 min 41.0 sec am335x-bone PASS: 0 min 33.5 sec imx6q-wandboard PASS: 0 min 15.7 sec omap3-tobi,3730storm PASS: 0 min 40.3 sec imx6dl-wandboard,wand-dual PASS: 0 min 16.8 sec omap3-beagle PASS: 0 min 56.5 sec arm-exynos_defconfig -------------------- exynos5250-arndale PASS: 0 min 30.0 sec arm-mvebu_defconfig ------------------- mirabox PASS: 0 min 16.9 sec armada-370-mirabox FAIL: 0 min 26.1 sec arm-sama5_defconfig ------------------- sama5d35ek PASS: 0 min 18.2 sec Console logs for failures ========================= arm-omap2plus_defconfig ----------------------- am335x-bone: FAIL: last 24 lines of boot log: --------------------------------------------- [ 2.024427] tps65217 0-0024: TPS65217 ID 0xf version 1.1 [ 2.096982] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [ 2.103428] davinci_mdio 4a101000.mdio: detected phy mask fffffffe [ 2.113581] libphy: 4a101000.mdio: probed [ 2.117987] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 [ 2.128217] Random MACID = 82:52:35:e8:61:0d [ 2.139545] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 2.151735] net eth0: initializing cpsw version 1.12 (0) [ 2.159965] net eth0: phy found : id is : 0x7c0f1 [ 2.164972] libphy: PHY 4a101000.mdio:01 not found [ 2.170082] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 5.237514] libphy: 4a101000.mdio:00 - Link is Up - 100/Half [ 5.257563] IP-Config: Complete: [ 5.260992] device=eth0, hwaddr=82:52:35:e8:61:0d, ipaddr=192.168.1.174, mask=255.255.255.0, gw=192.168.1.254 [ 5.271971] host=192.168.1.174, domain=, nis-domain=(none) [ 5.278287] bootserver=192.168.1.2, rootserver=192.168.1.2, rootpath= [ 5.285341] nameserver0=192.168.1.254 [ 5.315472] VFS: Mounted root (nfs filesystem) readonly on device 0:12. [ 5.324921] devtmpfs: mounted [ 5.329211] Freeing unused kernel memory: 380K (c0723000 - c0782000) ~$off # PYBOOT: Exception: ERROR: Timeout waiting for command: printenv bootargs. # PYBOOT: Time: 50.27 seconds. # PYBOOT: Result: FAIL arm-mvebu_defconfig ------------------- armada-370-mirabox: FAIL: last 24 lines of boot log: ---------------------------------------------------- can't open /dev/null: No such file or directory Starting logging: OK Starting network... mount: mounting none on /sys/kernel/debug failed: No such file or directory /bin/sh: can't access tty; job control turned off / # usb 1-1: new high-speed USB device number 2 using orion-ehci hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected usb 1-1.1: new high-speed USB device number 3 using orion-ehci usb-storage 1-1.1:1.0: USB Mass Storage device detected usb-storage 1-1.1:1.0: Quirks match for vid 05e3 pid 0723: 8000 scsi0 : usb-storage 1-1.1:1.0 usb 1-1.2: new high-speed USB device number 4 using orion-ehci usb-storage 1-1.2:1.0: USB Mass Storage device detected usb-storage 1-1.2:1.0: Quirks match for vid 05e3 pid 0723: 8000 scsi1 : usb-storage 1-1.2:1.0 scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 9451 PQ: 0 ANSI: 0 sd 0:0:0:0: [sda] Attached SCSI removable disk scsi 1:0:0:0: Direct-Access Generic STORAGE DEVICE 9451 PQ: 0 ANSI: 0 sd 1:0:0:0: [sdb] Attached SCSI removable disk ~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 26.15 seconds. # PYBOOT: Result: FAIL

11 years, 9 months

linus/master boot: 28 pass, 1 fail (v3.12-rc2-245-g30ceb4e)

by Kevin Hilman build bot

11 years, 9 months

[PATCH v2 0/4] perf: parse the dwarf backtrace info from .debug_frame section

by Jean Pihet

On ARM the debug info is not present in the .eh_frame sections but in .debug_frame instead, in dwarf format. This patch set uses libunwind to load and parse the dwarf debug info from the .debug_frame section if no .eh_frame_hdr section is found; also it sets the hooks in the perf_regs and libunwind code for ARMv7. Dependencies: . if present, libunwind >= 1.1 is needed to prevent a segfault when parsing the dwarf info, . libunwind needs to be configured with --enable-debug-frame to prevent a linkage error. Note: --enable-debug-frame is automatically selected on ARM). The generated perf has been tested on ARMv7 (OMAP4, Marvell Armada XP) and x86_64, using the following commands: perf record -g [dwarf] -- <binary> perf report --sort symbol --call-graph --stdio Jean Pihet (2): perf tools: Check libunwind for availability of dwarf parsing feature perf: parse the .debug_frame section in case .eh_frame is not present Will Deacon (2): ARM: perf: add support for perf registers API ARM: perf: wire up perf_regs and unwind support for ARM arch/arm/Kconfig | 2 + arch/arm/include/uapi/asm/Kbuild | 1 + arch/arm/include/uapi/asm/perf_regs.h | 23 +++++++++++ arch/arm/kernel/Makefile | 1 + arch/arm/kernel/perf_regs.c | 30 ++++++++++++++ tools/perf/arch/arm/Makefile | 3 ++ tools/perf/arch/arm/include/perf_regs.h | 54 +++++++++++++++++++++++++ tools/perf/arch/arm/util/unwind.c | 48 ++++++++++++++++++++++ tools/perf/config/Makefile | 7 +++- tools/perf/config/feature-tests.mak | 11 ++++- tools/perf/util/unwind.c | 71 +++++++++++++++++++++++++-------- 11 files changed, 232 insertions(+), 19 deletions(-) create mode 100644 arch/arm/include/uapi/asm/perf_regs.h create mode 100644 arch/arm/kernel/perf_regs.c create mode 100644 tools/perf/arch/arm/include/perf_regs.h create mode 100644 tools/perf/arch/arm/util/unwind.c -- 1.7.11.7

11 years, 9 months

[PATCH 0/4] driver core: Introduce initcall_driver() to eliminate boilerplate code

by Hanjun Guo

Lots of device drivers especially for platform/I2C/SPI bus devices, they want to be initialized earlier than other devices, so the driver use initcall such as subsys_initcall for the device initialization. But for those drivers, lots of them just do nothing special in xxx_initcall/module_exit, and produce lots of boilerplate. This patch set introduces a helper macro initcall_driver() to eliminate lots of boilerplate just like module_driver() did, and use it for platform/I2C/SPI bus devices. I use following command under the lastest kernel source code: $grep -r -E "*_initcall" drivers/ | cut -d":" -f1 |xargs grep -E "return platform_driver_register|return i2c_add_driver|return spi_register_driver" | cut -d":" -f1 | xargs grep "module_exit" | wc -l and get 205 hits, so if we use helper macro initcall_driver(), we can reduce thousands lines of code. Hanjun Guo (4): driver core: introduce helper macro initcall_driver() platform device: introduce helper macro initcall_platform_driver() i2c: introduce helper macro initcall_i2c_driver() spi: introduce helper macro initcall_spi_driver() include/linux/device.h | 27 +++++++++++++++++++++++++++ include/linux/i2c.h | 11 +++++++++++ include/linux/platform_device.h | 11 +++++++++++ include/linux/spi/spi.h | 11 +++++++++++ 4 files changed, 60 insertions(+) -- 1.7.9.5

11 years, 9 months

[PATCH] KVM: ARM: arch_timer: Initialize cntvoff at vcpu_init

by Christoffer Dall

Initialize the cntvoff at vcpu_init time, not before running the VCPUs at the first time because that will overwrite any potentially restored values from user space. Signed-off-by: Christoffer Dall <christoffer.dall(a)linaro.org> --- virt/kvm/arm/arch_timer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c index 8168437..2f6b5fe 100644 --- a/virt/kvm/arm/arch_timer.c +++ b/virt/kvm/arm/arch_timer.c @@ -181,6 +181,7 @@ void kvm_timer_vcpu_init(struct kvm_vcpu *vcpu) INIT_WORK(&timer->expired, kvm_timer_inject_irq_work); hrtimer_init(&timer->timer, CLOCK_MONOTONIC, HRTIMER_MODE_ABS); timer->timer.function = kvm_timer_expire; + vcpu->kvm->arch.timer.cntvoff = kvm_phys_timer_read(); } static void kvm_timer_init_interrupt(void *info) @@ -282,7 +283,6 @@ void kvm_timer_vcpu_terminate(struct kvm_vcpu *vcpu) int kvm_timer_init(struct kvm *kvm) { if (timecounter && wqueue) { - kvm->arch.timer.cntvoff = kvm_phys_timer_read(); kvm->arch.timer.enabled = 1; } -- 1.7.10.4

11 years, 9 months

next/master boot: 26 pass, 3 fail (next-20130927)

by Kevin Hilman build bot

Automated DT boot report for various ARM defconfigs. Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo'). Tree/Branch: next/master Git describe: next-20130927 Commit: a0cf1abc25 Add linux-next specific files for 20130927 Failed boot tests (console logs at the end) =========================================== armada-370-mirabox: FAIL: arm-multi_v7_defconfig armada-370-mirabox: FAIL: arm-mvebu_defconfig sama5d35ek: FAIL: arm-sama5_defconfig Full Report =========== arm-tegra_defconfig ------------------- tegra30-beaver PASS: 0 min 17.9 sec arm-omap2plus_defconfig ----------------------- am335x-boneblack PASS: 0 min 30.0 sec omap3-beagle-xm PASS: 0 min 49.8 sec am335x-bone PASS: 0 min 26.3 sec omap3-tobi,3530overo PASS: 0 min 42.3 sec omap4-panda PASS: 1 min 2.6 sec omap4-panda-es PASS: 1 min 10.4 sec omap3-tobi,3730storm PASS: 0 min 41.2 sec omap3-beagle PASS: 0 min 52.5 sec arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.5 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.3 sec imx6q-wandboard PASS: 0 min 15.1 sec arm-multi_v7_defconfig ---------------------- tegra30-beaver PASS: 0 min 15.1 sec am335x-boneblack PASS: 0 min 34.6 sec omap3-beagle-xm PASS: 0 min 51.8 sec armada-370-mirabox FAIL: 0 min 30.6 sec omap4-panda PASS: 1 min 1.2 sec omap4-panda-es PASS: 1 min 11.4 sec sun4i-a10-cubieboard PASS: 0 min 11.7 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.5 sec omap3-tobi,3530overo PASS: 0 min 40.7 sec am335x-bone PASS: 0 min 33.4 sec imx6q-wandboard PASS: 0 min 15.7 sec omap3-tobi,3730storm PASS: 0 min 39.7 sec imx6dl-wandboard,wand-dual PASS: 0 min 16.6 sec omap3-beagle PASS: 0 min 53.5 sec arm-exynos_defconfig -------------------- exynos5250-arndale PASS: 0 min 30.1 sec arm-mvebu_defconfig ------------------- armada-370-mirabox FAIL: 0 min 30.6 sec arm-sama5_defconfig ------------------- sama5d35ek FAIL: 0 min 13.8 sec Console logs for failures ========================= arm-multi_v7_defconfig ---------------------- armada-370-mirabox: FAIL: last 24 lines of boot log: ---------------------------------------------------- Connected to mirabox console [channel connected] (~$quit to exit) (user:khilman) is already connected ~$hardreset Command(mirabox console)> hardreset (user:jenkins) Reboot mirabox Reboot: mirabox ; ip9258 1 1 : off, sleep, on ~$off # PYBOOT: Exception: ERROR: Could not break into autoboot. # PYBOOT: Time: 30.59 seconds. # PYBOOT: Result: FAIL arm-mvebu_defconfig ------------------- armada-370-mirabox: FAIL: last 24 lines of boot log: ---------------------------------------------------- Connected to mirabox console [channel connected] (~$quit to exit) (user:khilman) is already connected ~$hardreset cu: write: Input/output error Connected. cu: waitpid: No child processes Command(mirabox console)> hardreset (user:jenkins) Reboot mirabox Connected. Disconnected. Reboot: mirabox ; ip9258 1 1 : off, sleep, on ~$off # PYBOOT: Exception: ERROR: Could not break into autoboot. # PYBOOT: Time: 30.59 seconds. # PYBOOT: Result: FAIL arm-sama5_defconfig ------------------- sama5d35ek: FAIL: last 24 lines of boot log: -------------------------------------------- Process swapper (pid: 1, stack limit = 0xdf854238) Stack: (0xdf855eb8 to 0xdf856000) 5ea0: 00000000 00000000 5ec0: c0538618 c0529a34 c0260628 c051dc20 df854000 c0508484 00000000 c051dc50 5ee0: 00000000 c052f2c8 00000006 c0529a34 c0564b80 c0008780 df83e1c0 c00cbc20 5f00: c056ca4c df83e1c0 c03caf00 00000010 c0564b80 c04e46d0 00000000 00000001 5f20: c098d215 c03df988 0000007d c002fd60 c0564b80 c04e46d0 c04a6dd0 c04e3f00 5f40: 00000006 00000006 00000000 c052f2c8 00000006 c0529a34 c0564b80 0000007d 5f60: c0529a40 c0508484 00000000 c0508ad0 00000006 00000006 c0508484 fff7cfb7 5f80: b4dff7fc c4edfdeb 00000000 c03c01e8 00000000 00000000 00000000 00000000 5fa0: 00000000 c03c01f0 00000000 c000e2d8 00000000 00000000 00000000 00000000 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 eaeecabe f7a1c7bd [<c025d5b4>] (ohci_init_driver+0xa8/0x100) from [<c051dc50>] (ohci_at91_init+0x30/0x84) [<c051dc50>] (ohci_at91_init+0x30/0x84) from [<c0008780>] (do_one_initcall+0xec/0x148) [<c0008780>] (do_one_initcall+0xec/0x148) from [<c0508ad0>] (kernel_init_freeable+0xe8/0x1b0) [<c0508ad0>] (kernel_init_freeable+0xe8/0x1b0) from [<c03c01f0>] (kernel_init+0x8/0xe4) [<c03c01f0>] (kernel_init+0x8/0xe4) from [<c000e2d8>] (ret_from_fork+0x14/0x3c) Code: e5840048 e584104c e5842050 e5843054 (e5953000) ---[ end trace 2ce01bf77138c668 ]--- Kernel panic -~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: Kernel panic # PYBOOT: Time: 13.85 seconds. # PYBOOT: Result: FAIL

11 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel