On 2 December 2014 at 12:51, pi-cheng.chen wrote:
> Add 2 new kind of event for running a memory or a io bounded load.
> "mem" name for a load is memory bounded, and "iorun" name for a load is io
> bounded. The default file to be written to create the load is /dev/null and
> the device/file could
Add 2 new kind of event for running a memory or a io bounded load.
"mem" name for a load is memory bounded, and "iorun" name for a load is io
bounded. The default file to be written to create the load is /dev/null and
the device/file could be specified with "io_device" key in "global" section.
E.
On 2 December 2014 at 15:09, Viresh Kumar wrote:
> On 2 December 2014 at 12:34, pi-cheng.chen wrote:
>> Add 2 new kind of event for running a memory or a io bounded load.
>> "mem" name for a load is memory bounded, and "iorun" name for a load is io
>> bounded. The default file to be written to cr
On 2 December 2014 at 12:34, pi-cheng.chen wrote:
> Add 2 new kind of event for running a memory or a io bounded load.
> "mem" name for a load is memory bounded, and "iorun" name for a load is io
> bounded. The default file to be written to create the load is /dev/null and
> the device/file could
Add 2 new kind of event for running a memory or a io bounded load.
"mem" name for a load is memory bounded, and "iorun" name for a load is io
bounded. The default file to be written to create the load is /dev/null and
the device/file could be specified with "io_device" key in "global" section.
E.
On Monday 01 December 2014 16:32:21 Shawn Guo wrote:
> Is it a valid or supported use case to build LSK 3.14 kernel with
> android-toolchain? I can build a LSK 3.14 kernel with Linux toolchain
> gcc-linaro-arm-none-eabi-4.9-2014.09, which boots fine on my board.
> When I build the same kernel with
== Progress ==
* ILP32 support in linux-linaro: sanity tested with 64-bit userland (LTP syscall tests), 1 (out of 881) test failed on
ILP32-enabled kernel only - regression (CARD-1161: 50%)
* llct updated to v3.18-rc6, the schedule for linux-linaro updates for 14.12
published on the wiki (CARD-
== Progress ==
* New script to run KVM tests with trusty/utopic guests (DEVPLAT-264 60%)
* Moving CI towards utopic and other CI fixes (30%)
== Plans ==
* Finish utopic move for kvm and xen
* Finish DEVPLAT-264 (stable guests for kvm)
___
linaro-dev mai
Hi all,
Is it a valid or supported use case to build LSK 3.14 kernel with
android-toolchain? I can build a LSK 3.14 kernel with Linux toolchain
gcc-linaro-arm-none-eabi-4.9-2014.09, which boots fine on my board.
When I build the same kernel with
android-toolchain-eabi-4.9-2014.09-x86, the kernel
