linaro-dev September 2013

linaro-dev@lists.linaro.org

29 participants
29 discussions

by Renato Golin

One example of the kind of results that come from a GSOC project: http://flang-gsoc.blogspot.ie/2013/09/end-of-gsoc-report.html Might be worth thinking about it next year? cheers, --renato

10 years, 11 months

[PATCH V2 Resend 0/4] Create sched_select_cpu() and use it for workqueues and timers

by Viresh Kumar

Hi All, This is V2 Resend of my sched_select_cpu() work. Resend because didn't got much attention on V2. Including more guys now in cc :) In order to save power, it would be useful to schedule work onto non-IDLE cpus instead of waking up an IDLE one. To achieve this, we need scheduler to guide kernel frameworks (like: timers & workqueues) on which is the most preferred CPU that must be used for these tasks. This patchset is about implementing this concept. - The first patch adds sched_select_cpu() routine which returns the preferred cpu which is non-idle. - Second patch removes idle_cpu() calls from timer & hrtimer. - Third patch is about adapting this change in workqueue framework. - Fourth patch add migration capability in running timer Earlier discussions over v1 can be found here: http://www.mail-archive.com/linaro-dev@lists.linaro.org/msg13342.html Earlier discussions over this concept were done at last LPC: http://summit.linuxplumbersconf.org/lpc-2012/meeting/90/lpc2012-sched-timer… Module created for testing this behavior is present here: http://git.linaro.org/gitweb?p=people/vireshk/module.git;a=summary Following are the steps followed in test module: 1. Run single work on each cpu 2. This work will start a timer after x (tested with 10) jiffies of delay 3. Timer routine queues a work... (This may be called from idle or non-idle cpu) and starts the same timer again STEP 3 is done for n number of times (i.e. queuing n works, one after other) 4. All works will call a single routine, which will count following per cpu: - Total works processed by a CPU - Total works processed by a CPU, which are queued from it - Total works processed by a CPU, which aren't queued from it Setup: ----- - ARM Vexpress TC2 - big.LITTLE CPU - Core 0-1: A15, 2-4: A7 - rootfs: linaro-ubuntu-nano Results: ------- Without Workqueue Modification, i.e. PATCH 3/3: [ 2493.022335] Workqueue Analyser: works processsed by CPU0, Total: 1000, Own: 0, migrated: 0 [ 2493.047789] Workqueue Analyser: works processsed by CPU1, Total: 1000, Own: 0, migrated: 0 [ 2493.072918] Workqueue Analyser: works processsed by CPU2, Total: 1000, Own: 0, migrated: 0 [ 2493.098576] Workqueue Analyser: works processsed by CPU3, Total: 1000, Own: 0, migrated: 0 [ 2493.123702] Workqueue Analyser: works processsed by CPU4, Total: 1000, Own: 0, migrated: 0 With Workqueue Modification, i.e. PATCH 3/3: [ 2493.022335] Workqueue Analyser: works processsed by CPU0, Total: 1002, Own: 999, migrated: 3 [ 2493.047789] Workqueue Analyser: works processsed by CPU1, Total: 998, Own: 997, migrated: 1 [ 2493.072918] Workqueue Analyser: works processsed by CPU2, Total: 1013, Own: 996, migrated: 17 [ 2493.098576] Workqueue Analyser: works processsed by CPU3, Total: 998, Own: 993, migrated: 5 [ 2493.123702] Workqueue Analyser: works processsed by CPU4, Total: 989, Own: 987, migrated: 2 V2->V2-Resend ------------- - Included timer migration patch in the same thread. V1->V2 ----- - New SD_* macros removed now and earlier ones used - sched_select_cpu() rewritten and it includes the check on current cpu's idleness. - cpu_idle() calls from timer and hrtimer removed now. - Patch 2/3 from V1, removed as it doesn't apply to latest workqueue branch from tejun. - CONFIG_MIGRATE_WQ removed and so is wq_select_cpu() - sched_select_cpu() called only from __queue_work() - got tejun/for-3.7 branch in my tree, before making workqueue changes. Viresh Kumar (4): sched: Create sched_select_cpu() to give preferred CPU for power saving timer: hrtimer: Don't check idle_cpu() before calling get_nohz_timer_target() workqueue: Schedule work on non-idle cpu instead of current one timer: Migrate running timer include/linux/sched.h | 16 ++++++++++-- include/linux/timer.h | 2 ++ kernel/hrtimer.c | 2 +- kernel/sched/core.c | 69 +++++++++++++++++++++++++++++++-------------------- kernel/timer.c | 50 ++++++++++++++++++++++--------------- kernel/workqueue.c | 4 +-- 6 files changed, 91 insertions(+), 52 deletions(-) -- 1.7.12.rc2.18.g61b472e

11 years, 1 month

[PATCH 0/5] libhugetlbfs - Aarch64 support and some fixes

by Steve Capper

Hello, This series adds Aarch64 support and makes some minor tweaks. The first two patches of this series add Aarch64 support to libhugetlbfs. (Starting from 3.11-rc1, the Linux Kernel supports HugeTLB and THP for ARM64). Some general changes are also made: PROT_NONE is added to the mprotect unit test, and the linkhuge_rw test is enabled for 64 bit where there aren't any custom ldscripts. The final patch clears up the superfluous ARM ld.hugetlbfs HTLB_LINK logic. Any comments would be appreciated. Cheers, -- Steve Steve Capper (5): Aarch64 support. Aarch64 unit test fixes. Add PROT_NONE to the mprotect test. Add linkhuge_rw test to 64 bit && !CUSTOM_LDSCIPTS Cleanup ARM ld.hugetlbfs HTLB_LINK logic Makefile | 7 +++++++ ld.hugetlbfs | 7 +------ sys-aarch64elf.S | 34 ++++++++++++++++++++++++++++++++++ tests/Makefile | 2 +- tests/icache-hygiene.c | 7 ++++--- tests/mprotect.c | 6 ++++++ tests/mremap-expand-slice-collision.c | 2 +- 7 files changed, 54 insertions(+), 11 deletions(-) create mode 100644 sys-aarch64elf.S -- 1.8.1.4

11 years, 2 months

M0 and M3 patches in linaro toolchains

by Wookey

Debconf13 (last week) considered the matter of bare-metal cross-toolchains in Debian. Ideally we would have one toolchain source package from which the existing linux native compilers, and cross-compilers are built, including bare-metal cross-compilers. There is already mechanism for adding patches for particular gcc builds, so so long as the patch set is manageable and trackable, this would be nice, and futureproof, as eventually the patch set should just evaporate as it gets upstreamed. The alternative it to simply repack the existing linaro cross-toolchain sources, but them we get to keep doing that for new releases, and we have gratuitous extra copies of gcc sources and corresponding differences between A* and M* toolchains/versions. The linaro embedded toolchains (https://launchpad.net/gcc-arm-embedded/4.7/4.7-2013-q1-update) are good, and work, both for M0 and M3. But building nominally the same thing from upstream gcc gets something where M3 works but M0 doesn't. Also they are gcc 4.7 based whilst Debian is moving to a 4.8 default. We peered at checkouts from linaro and upstream and tried to work out what the linaro patch-set for this toolchain is, and exactly where it branched off upstream, but it was confusing with a lot of noise due to version skew around some actually relevant changes. So, in order to work out if we can in fact build our bare-metal toolchains from the same sources as the existing toolchains we need to know what the actual patch-set you are maitaining looks like, and what is already upstreamed in which gcc branch/release and when the remaining patches will go upstream. Also what the 4.7 vs 4.8 status is. Knowing how this stuff is tracked might be even more useful over the longer term. Is there such info online somewhere? If not please elaborate. A mechanism for keeping the (newly-formed) Debian cross-compiler team sufficiently in the loop is probably what's needed in the longer term, unless this is all just about to get upstreamed anyway and the issue will soon become moot...? There was also discussion around the concept of making existing linux-arm cross-compilers, with M0 and M3 support included, and using spec-file jiggery-pokery to get them to DTRT for M* targets. This should be possible, but advice from anyone who's every actually tried on the gotchas would be good. cheers Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/

11 years, 2 months

Can't build correct kernel for 13.07 linaro-ubuntu on pandaboard

by Chao Xu

Hi, I tried to build linaro kernel for pandaboard. I have tried everything what I can think of but the kernel still can't boot correctly. Any help will be appreciated. Here is what I did: 1. I flash the 13.07 linaro-ubuntu-pandaboard image into the sd card ( http://releases.linaro.org/13.07/ubuntu/panda). This image works fine. 2. I clone the kernel source code from git:// git.linaro.org/kernel/linux-linaro-stable.git. 3. checkout the lsk 13.07 tag. 4. copy the config file from original image (i.e. /boot/config-3.10.1.0-1-linaro-omap). 5. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- CFLAGS="-O" LOADADDR=0x80008000 uImage The cross compiler on my machine is gcc-4.7-arm-linux-gnueabihf-base 6. From pandaboard, I load the built uImage via scp. The problem I met: 1. In most cases, the kernel can't boot correctly. And the terminal keeps printing "hub 1-1:1.0: hub_port_status failed (err = -71)". 2.Sometime, the kernel can finish booting. But the terminal prints for several times the aforementioned error message after booting. Plus, I don't have any module running, 'lsmod' shows nothing. Please help! Thank you. -- Regards, Chao Xu

11 years, 2 months

Ondemand governor clarifications

by Ryan

Hi, I wanted to know if the ondemand governor scales down the frequency to a minimum when the load comes below up_threshold? I understand that 1) Every now and then, the governor work queue runs and checks for "load" in percentage. If load > 95 ; it bumps the frequency to maximum; ie. if the idle time is less than 5% ; the cpu will run at maximum 2) If load < 90% ; it bumps the frequency down little bit; It continues to do this till minimum; So the rate of decrease of frequency to minimum is very slow; So, the frequency decrease to minimum will take a long time to reach minimum (depends on sampling time). Is this correct. /Ryan

11 years, 2 months

CTS test report for Calender week 39 Linaro Android Jellybean TI-panda builds on Lava dashboard.

by Soumya Basak

CTS results summary for Calender Week 39: Here is the cts test results summary on Lava dashboard Linaro Android Jellybean TI Panda builds; http://validation.linaro.org/dashboard/image-reports/linaro-android-member-… Job_id: http://validation.linaro.org/dashboard/streams/private/team/linaro/android-… http://validation.linaro.org/scheduler/job/74675 cts test result bundle stream : http://validation.linaro.org/dashboard/streams/private/team/linaro/android-… Please refer to the cts test report: https://drive.google.com/a/linaro.org/?tab=mo#folders/0BwB-fT5LL31CNEhIZ0p3… Thank You Best Regards Soumya Basak.

11 years, 2 months

Test Result Summary of Linux Linaro ubuntu 13.09 Release.

by Botao Sun

Linaro 13.09 Release (Calendar Week 39): Here is the test result summary for Linux Linaro ubuntu Raring image on following targets: 1) ARM Versatile Express A9; 2) ARM Versatile Express A9 ALIP; 3) Samsung Arndale; 4) TI Panda 4430; 5) TI Panda 4460; 6) Highbank. 1. ARM Versatile Express A9 + Linux Linaro Raring (Column AN): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV… 2. ARM Versatile Express A9 + Linux Linaro Raring ALIP (Column G): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV… 3. Samsung Arndale + Linux Linaro Raring (Column AG): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdGZJS… 4. TI Panda 4430 + Linux Linaro Raring (Column AN): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ… 5. TI Panda 4460 + Linux Linaro Raring (Column AN): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ… 6. Highbank + Linux Linaro Raring (Column D): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0ApLb2E5n36JpdFBnZ… For consolidated test result spreadsheet, please refer to this link: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdDdWZ… For test result summary of calendar Week 38, please refer to attachment. Thank you. Best Regards Botao Sun

11 years, 2 months

Test Result Summary of Linaro Openembedded 13.09 release

by Soumya Basak

Linaro Openembedded 13.09 Release (Calender Week: 39): Here is the test result summary for Linaro Openembedded 13.09 release images. [1] Linaro Openembedded Minimal Image (Column: AK) Result Spreadsheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdDhwR… [2] Linaro Openembedded Lamp Image (Column: AK) Result Spreadsheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdDhwR… [3] Linaro Openembedded LEG-Java-ARMv8 Image (Column: N) Result Spreadsheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdDhwR… Please refer to the result spreadsheets for details test results. Thank You Best Regards Soumya Basak.

11 years, 2 months

Test Result Summary of Linaro Android Jellybean 13.09 release.

by Soumya Basak

Linaro Android Jellybean 13.09 Release (Calender Week 39): Here is the test result summary for Linaro Android Jellybean images on following boards: [1] TI-Pandaboard 4460; [2] TI-Pandaboard 4430; [3] Samsung Arndale; [4] Galaxy Nexus; [5] ARM Versatile Express A9; [6] ARM Versatile Express TC2; [7] LSK ARM Versatile Express TC2; [1] TI-Pandaboard 4460 + Linaro Android Jellybean 4.3 (Column: BC) Result Spreadsheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… [2] TI-Pandaboard 4430 + Linaro Android Jellybean 4.3 (Column: BC) Result Spreadsheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… [3] Samsung Arndale + Linaro Android Jellybean 4.3 (Column: M) Result Spreadsheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AuNOCeo15fRHdDFaR… [4] Galaxy Nexus + Linaro Android Jellybean 4.3 (Column: H) Result Spreadsheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AuNOCeo15fRHdFhhe… [5] ARM Versatile Express A9 + Linaro Android Jellybean 4.3 (Column: BC) Result Spreadsheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… [6] ARM Versatile Express TC2 + Linaro Android Jellybean 4.3 (Column: P) Result Spreadsheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… [7] LSK ARM Versatile Express TC2 + Linaro Android Jellybean (Column: B) Result Spreadsheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… Please refer to the Result Spreadsheet for details test results. Thank You Best Regards Soumya Basak.

11 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev September 2013