+ Linaro Dev mailing list
Hi Phung-Te,
I don't have Samsung Arndale Octa board on my hand, haven't started testing
on it.
@Fathi, do you know anything about the u-boot source code for Arndale Octa?
Thanks.
Best Regards
Botao Sun
Hello Botao,
I am looking for the source of u-boot for arndale-octa and couldn't find
it. Your u-boot git, both stable and next only have support for arndale,
not arndale-octa.
I could get to the binary which worked fine:
arndale-octa-saucy_server_20140323-616.img.gz
Can you please point me to the source of that build.
Thank you.
Phung-Te
On Fri, Mar 28, 2014 at 2:58 PM, Botao Sun (Google Drive) <
Botao.Sun(a)linaro.org> wrote:
> I've shared an item with you.
> [image: Spreadsheet] Arndale Linux Linaro Test Result<https://docs.google.com/spreadsheet/ccc?key=0AgB-fT5LL31CdGZJSFdTUWFFYVdhZl…>
> Google Drive: create, share, and keep all your stuff in one place. [image:
> Logo for Google Drive] <https://drive.google.com>
>
Hello,
It looks like README file in powertop branch is out of sync with how
powertop should be actually built.
It should be updated.
diff --git a/README b/README
index 2961eba..d83b315 100644
--- a/README
+++ b/README
@@ -2,9 +2,10 @@
------------------------------
To build and install PowerTOP type the following commands,
- ./configure
- ./make
- ./make install
+ autoreconf -sfi
+ ./configure
+ make
+ make install
Note: For Android (running Intel Architecture ) there is a Android.mk
that was provided by community members, and at this time is supported
--
Thanks,
-Meraj
Hi All,
In arch/arm64/include/asm/barrier.h, there is the definition of
smp_mb()/smp_rmb()/smp_wmb() for arm64. I noticed that all the 3 macors
are using "dmb ishxx", which is only affect the cluster of the CPU
executing the instruction. But in the big.LITTLE system, there will be 2
cluster. So the smp_mb()/smp_rmb()/smp_wmb() cannot affect all the CPU
in the system.
Is there other considerations so that smp_mb()/smp_rmb()/smp_wmb() are
implemented to "only affecting inner sharable cores"?
Best Regards,
Kelvin K. Li
---------------------------------------------------------------
Software Team, VIA Technologies, Inc.
5F, VIA Tower, 1 Zhongguancun East Road,
Haidian District, Beijing, 100084
Tel: 86-10-59852288 ext.3620
mailto: kelvinkli(a)via-alliance.com
Signed-off-by: Sanjay Singh Rawat <sanjay.rawat(a)linaro.org>
---
- This will help in catching issue like https://lkml.org/lkml/2014/3/25/122
- Tested on my x86 dev m/c
Output:
running hotplug stress on cpu : cpu1
pass: cpu hotplug count = 200 duration = 16.98 seconds
running hotplug stress on cpu : cpu2
pass: cpu hotplug count = 200 duration = 16.36 seconds
running hotplug stress on cpu : cpu3
pass: cpu hotplug count = 200 duration = 15.05 seconds
- Issue: For a hotplug count of 500 the system just hangs. Need to
manually restart.
Is it safe to simply plugout the cpu? What will happend to the tasks
in the cpu runqueue.
---
cpuhotplug/cpuhotplug_09.sh | 70 ++++++++++++++++++++++++++++++++++++++++++
cpuhotplug/cpuhotplug_09.txt | 1 +
2 files changed, 71 insertions(+)
create mode 100755 cpuhotplug/cpuhotplug_09.sh
create mode 100644 cpuhotplug/cpuhotplug_09.txt
diff --git a/cpuhotplug/cpuhotplug_09.sh b/cpuhotplug/cpuhotplug_09.sh
new file mode 100755
index 0000000..be0c91c
--- /dev/null
+++ b/cpuhotplug/cpuhotplug_09.sh
@@ -0,0 +1,70 @@
+#!/bin/bash
+#
+# PM-QA validation test suite for the power management on Linux
+#
+# Copyright (C) 2014, Linaro Limited.
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program 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 General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+#
+# Contributors:
+# Sanjay Singh Rawat <sanjay.rawat(a)linaro.org>
+# - initial API and implementation
+#
+
+# URL : https://wiki.linaro.org/WorkingGroups/PowerManagement/Resources/TestSuite/P…
+
+source ../include/functions.sh
+STRESS_COUNT=200
+
+cpuhotplug_stress() {
+ local cpu=$1
+ local dirpath=$CPU_PATH/$1
+ local state=
+ local start=
+ local end=
+ shift 1
+
+ if [ "$cpu" == "cpu0" ]; then
+ # skipping main cpu
+ return 0
+ fi
+
+ echo "running hotplug stress on cpu :" $cpu
+ start=$(echo $(awk '{print $1}' /proc/uptime))
+
+ for i in $(seq 1 $STRESS_COUNT);
+ do
+ set_offline $cpu
+ state=$(get_online $cpu)
+ if [ $state -ne 0 ]; then
+ echo "fail: cpu offline failed at " $i
+ return 1
+ fi
+
+ set_online $cpu
+ state=$(get_online $cpu)
+ if [ $state -ne 1 ]; then
+ echo "fail: cpu online failed at " $i
+ return 1
+ fi
+ done
+
+ end=$(echo $(awk '{print $1}' /proc/uptime))
+ echo "pass: cpu hotplug in/out count =" $i "duration =" $(echo "$end-$start" | bc) "seconds"
+ return 0
+}
+
+for_each_cpu cpuhotplug_stress
+test_status_show
diff --git a/cpuhotplug/cpuhotplug_09.txt b/cpuhotplug/cpuhotplug_09.txt
new file mode 100644
index 0000000..5b0f8ac
--- /dev/null
+++ b/cpuhotplug/cpuhotplug_09.txt
@@ -0,0 +1 @@
+test to stress cpu hotplug feature
--
1.7.10.4
FYI: for those interested in Fedora, I thought I would pass on
an announcement from Paul Whalen recently sent to the fedora-arm
mailing list...you can now pick a remix image using the links
highlighted below...
Good afternoon folks,
David Marlin has posted a new Aarch64 Fedora Rawhide Remix for those
interested in upgrading from the F19 bootstrap image.
The remix includes a lookaside repository[1] to provide a patched
kernel and packages not yet built for aarch64.
Instructions for downloading and using the remix have been added to
the Quickstart[2] page.
Paul
[1] - http://dmarlin.fedorapeople.org/yum/f21/
[2] - https://fedoraproject.org/wiki/Architectures/ARM/AArch64/QuickStart
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Linaro Enterprise Group
al.stone(a)linaro.org
-----------------------------------
On 18/04/2014 16:44, Richard Henderson wrote:
> On 04/18/2014 07:00 AM, Mian M. Hamayun wrote:
>> Hello Peter & All,
>>
>> I am trying to figure out a problem in qemu on aarch64 (with kvm enabled). I
>> have found this problem in many different versions of qemu
>> (v2.0.0-rc3/rc2/rc1/rc0, master 2d03b49), and I believe that either I am
>> missing something common in all of these versions or its a genuine bug in qemu
>> on aarch64.
>>
>> The problem is triggered by virtqueue_notify() function (in virtio_ring.c) from
>> the guest kernel and fails in the qemu_coroutine_new() while trying to do the
>> swapcontext(&old_uc, &uc) (see coroutine-ucontext.c:164). The
>> sigsetjmp(old_env, 0) just before the swapcontext() call seems to work fine, as
>> it returns 0, and then we invoke the swapcontext().
>>
>> The host kernel reports:
>> "qemu-system-aar[596]: bad frame in sys_rt_sigreturn: pc=004462e0
>> sp=7f8020f000" and kills the qemu process due to segmentation fault. The
>> pc=004462e0 is for the coroutine_trampoline() but we don't actually reach it,
>> when this particular crash happens.
>>
>> Just to give you an idea of the code I am talking about:
>>
>> $~/qemu[master]$ git blame -L 159,166 coroutine-ucontext.c
>> 00dccaf1 (Kevin Wolf 2011-01-17 16:08:14 +0000 159) makecontext(&uc,
>> (void (*)(void))coroutine_trampoline,
>> 00dccaf1 (Kevin Wolf 2011-01-17 16:08:14 +0000 160) 2,
>> arg.i[0], arg.i[1]);
>> 00dccaf1 (Kevin Wolf 2011-01-17 16:08:14 +0000 161)
>> 6ab7e546 (Peter Maydell 2013-02-20 15:21:09 +0000 162) /* swapcontext() in,
>> siglongjmp() back out */
>> 6ab7e546 (Peter Maydell 2013-02-20 15:21:09 +0000 163) if
>> (!sigsetjmp(old_env, 0)) {
>> 00dccaf1 (Kevin Wolf 2011-01-17 16:08:14 +0000 164)
>> swapcontext(&old_uc, &uc);
>> 00dccaf1 (Kevin Wolf 2011-01-17 16:08:14 +0000 165) }
>> 00dccaf1 (Kevin Wolf 2011-01-17 16:08:14 +0000 166) return &co->base;
>>
>> My qemu configure/run commands are:
>>
>> ./configure --target-list=aarch64-softmmu \
>> --cross-prefix=aarch64-linux-gnu- \
>> --enable-fdt *--enable-kvm* --disable-werror \
>> --audio-drv-list="" --static
>>
>> ./qemu-system-aarch64 \
>> *-enable-kvm* -nographic -kernel Image \
>> -drive if=none,file=disk_oe64.img,id=fs \
>> -device virtio-blk-device,drive=fs \
>> -m 1024 -M virt -cpu host \
>> -append "earlyprintk console=ttyAMA0 mem=1024M rootwait root=/dev/vda rw
>> init=/bin/sh"
>>
>> Any ideas/comments on how to resolve this issue?
> Note that a patch has just gone into glibc to rewrite setcontext et al for
> aarch64. I'd try using git glibc before looking too much deeper.
>
>
> r~
>
It seems right to me as well, as the setcontext related bug (for
aarch64) has recently been posted/fixed in glibc:
https://sourceware.org/bugzilla/show_bug.cgi?id=16629
I have also tested the example posted at:
https://sourceware.org/bugzilla/attachment.cgi?id=7435
and I get the following output on x86_64:
start f2
start f1
finish f2
finish f1
{ss_sp: (nil), ss_flags: 2, ss_size: 0}
{ss_sp: (nil), ss_flags: 2, ss_size: 0}
and this one on AArch64:
start f2
start f1
finish f2
finish f1
{ss_sp: (nil), ss_flags: 2, ss_size: 0}
*{ss_sp: 0x7ff7e723f0, ss_flags: 0, ss_size: 8192}*
I will first look into updating my glibc for AArch64 before coming back
to qemu.
Thanks for your support,
Hamayun