Hi,
I've got a pthread test that is the fall out of a bug fix which is a good test
of kernel and libc and would like to add it into Lava.
I'm told that I currently have to pick a hardware pack and image - but for
this case what I really want to do is to create a test that can be used
as a regression test that gets run on whatever the latest kernel is on
any of a set of platforms (basically anything of Panda speed or similar/faster).
mwhudson suggested I posted that requirement here.
Thoughts?
Dave
2011/7/25 Jim Huang <jserv(a)0xlab.org>:
[...]
> Recently, Kito Cheng (in Cc. list) is improving the support of Android
> prelink, and hopefully we would submit patches to AOSP soon.
It is pitty that we can not submit to AOSP still. However, the
patches are already public:
https://gitorious.org/+0xlab
Please check team activity during Oct 28 to Nov 6:
bionic/
GNU-style hash support for linker
build/
Update link script for gnu-sytle hash
Build library and executable with gnu-sytle hash table
GNU-sytle hash support for soslim
GNU-sytle hash support for apriori
Build with partial global prelink
Support partial global prelink for apriori
Build with prelinking executable
Support prelink executable with '-e/--prelink-executable' flag
Reorder DT_NEEDED entries in apriori
Build with incremental global prelink
Support incremental global prelink mode for apriori
external/elfcopy/
Basic GNU-sytle hash support for elfcopy
external/elfutil/
Add SHT_GNU_HASH, DT_GNU_HASH in libelf/elf.h
Sincerely,
Jim Huang (jserv)
http://0xlab.org/
Hello list,
Recently, we already released 0xbench version 1.1.5, and you can get
the latest binary/source here:
http://code.google.com/p/0xbench/downloads/listhttp://gitorious.org/0xbench
Changes since version 1.1.1:
- Add SunSpider JavaScript benchmark
- Allow customized result output path
- Support dashboard bundle format used in Linaro Automated Validation
Architecture
- Enable detailed report of libmicro and UnixBench
- Android 2.3+ build fixes
Also, you can install 0xbench on your Android devices through Android Market.
NOTE: due to the expiration of previous key for Android Market, we
have to rename the package and then upload to Marketplace again.
Therefore, the package namespace is now changed from
org.zeroxlab.benchmark to org.zeroxlab.zeroxbenchmark. We feel sorry
for inconvenience.
The next version will be 1.2.x, and glmark2 [*] is known to be part of
test cases.
Sincerely,
Jim Huang (jserv)
http://0xlab.org/
[*] https://launchpad.net/glmark2
2010/8/18 Jim Huang <jserv(a)0xlab.org>:
> Hello list,
>
> We are proud to announce the release of 0xBench, an open source
> Android benchmarking app developed by 0xlab.
>
> 0xBench comes with several built-in benchmarks, such as Linpack,
> Scimark2, and LibMicro. 0xBench itself could be extended as well.
> Developers can add their own benchmarks (either in native C or Java)
> to suit their needs. Please check the project page for details:
> http://code.google.com/p/0xbench/
>
> Documentation in Wiki: http://code.google.com/p/0xbench/w/list
>
> As usual, 0xBench GIT repository is hosted in Gitorious:
> http://gitorious.org/0xbench/
>
> 0xBench is now on the Android Market. If you wish to try it on your
> phone, please search for “0xBench” in the Market. In addition to
> 0xBench, we are also introducing a website called 0xBenchWeb, a simple
> web service that stores and visualizes your benchmarking results.
> After finish running benchmarks on your phone, you can choose to
> upload your results to 0xBenchWeb.
> http://0xbenchmark.appspot.com/
Hi All,
I was migrating changes from GB(K 2.6.35) to K 3.0 but every
time my PMEM allocation in board file leads to crash the kernel before
serial up. Now I am
taking CAF kernel as reference but the
change in MACHINE_START structure(addition of init_early) in CAF code is
working fine.Please
tell why it is crashing without init_early
which is not present in K 2.6.35 and it was working fine and also the
associated changes to this.
regards
sandeep
The sched_mc feature has been originally designed to improve power
consumption of multi-package system and several architecture functions
are available to tune the topology and the scheduler's parameters when
scheduler rebuilds the sched_domain hierarchy (change the
sched_mc_power_savings level). This patches series is a trial to
improve the power consumption of dual and quad cortex-A9 when the
sched_mc_power_savings is set to 2. The following patch's policy is to
accept up to 4 threads (can be configured) in the run queue of a core
before starting to load balance if cpu runs at low frequencies but to
accept only 1 thread for high frequencies, which is the normal
behaviour. The goal is to use only one cpu in light load situation and
both cpu in heavy load situation
Patches [1-3] modify the ARM cpu topology according to
sched_mc_power_savings value and Cortex id
Patch [4] enables ARCH_POWER feature of the scheduler
Patch [5] adds ARCH_POWER function for ARM platform
Patches [6-7] modify the cpu_power of CA-9 according to
sched_mc_power_savings' level and current frequency. The main goal is
to increase the capacity of a core when using low cpu frequency in
order to pull tasks on this core. Note that this behaviour is not
really advised but it can be seen as an intermediate step between the
use of cpu hotplug (which is not a power saving feature) and a new
load balancer which will take into account low load situation on dual
core.
Patch [8] ensures that cpu0 is used in priority when only one CPU is running
Patch [9] adds some debugfs interface for test purpose
Patch [10] ensures that the cpu_power will be update periodically
Patch [11] fixes an issue around the trigger of ilb.
TODO list:
-remove useless start of ilb when the core has capacity.
-add a method (DT, sysfs, ...) to set threshold for using 1 or 2 cpus
for dual CA-9
-irq balancing
The tests hereafter have been done on a u8500 with kernel linaro-3.1.
They check that there is no obvious lost of performance when
sched_mc=2.
sysbench --test=cpu --num-threads=12 --max-time=20 run
Test execution summary: sched_mc=0 sched_mc=2 cpu hotplug
total number of events: 665 664
336
per-request statistics:
min: 92.68ms 70.53ms 618.89ms
avg: 361.75ms 361.38ms 725.29ms
max: 421.08ms 420.73ms 840.74ms
approx. 95 percentile: 402.28ms 390.53ms 760.17ms
sysbench --test=threads --thread-locks=9 --num-threads=12 --max-time=20 run
Test execution summary: sched_mc=0 sched_mc=2 cpu hotplug
total number of events: 10000 10000 3129
per-request statistics:
min: 1.62ms 1.70ms
13.16ms
avg: 22.23ms 21.87ms
76.77ms
max: 153.52ms 133.99ms 173.82ms
approx. 95 percentile: 54.12ms 52.65ms 136.32ms
sysbench --test=threads --thread-locks=2 --num-threads=3 --max-time=20 run
Test execution summary: sched_mc=0 sched_mc=2 cpu hotplug
total number of events: 10000 10000 10000
per-request statistics:
min: 1.38ms 1.38ms
5.70ms
avg: 4.67ms 5.37ms
11.85ms
max: 36.84ms 32.42ms 32.58ms
approx. 95 percentile: 14.34ms 12.89ms 21.30ms
cyclictest -q -t -D 20
Only one cpu is used during this test when sched_mc=2 whereas both cpu
are used when sched_mc=0
Test execution summary: sched_mc=0 sched_mc=2 cpu hotplug
Avg, Max: 15, 434 19, 2145 17, 3556
Avg, Max: 14, 104 19, 1686 17, 3593
Regards,
Vincent
Hi,
Snowball V2 boards are no longer supported. Daily builds are now disabled.
Linaro engineers, please go through your support channels for a
replacement board.
Cheers,
--
Fathi Boudra
Linaro Release Manager | Validation Project Manager
Linaro.org | Open source software for ARM SoCs