== 64 bit atomics ==
* Nailed one more of the membase tests; again this was a test
harness race condition (which I've reported here:
http://code.google.com/p/moxi/issues/detail?id=2&thanks=2&ts=1321037460 )
In this case there were two calls to write) performed on the
server, yet the test client performed a single read and
compared the result to what it was expecting; and got lucky on x86 and
about half the time on ARM in that the
server data managed to all get read by the 1st read.
I think this leaves one more case - that I've seen rarely.
== Qemu ==
* Tested Peter's 11.11 pre release; ran into a couple of issues
(vexpress without sound causing hangs, and
the Linaro 11.10 Beagle and Overo images not running X). Also
filed a couple of bugs in l-i-f-ui that
I tripped over while testing it.
== String routines ==
* The new newlib A15 optimised memcpy is slower on an A9 than my
routines; posted to newlib list
asking what the normal way of dealing with a bunch of different
routines is. Would it make sense to get
gcc to define a GCC_ARM_TUNE_CORTEX_A-whatever ?
== Other ==
* Watched the Youtube video of the Kernel/Toolchain discussion -
for those who didn't attend,
I'd encourage a check of the Youtube videos, they're pretty nicely done.
* Got pulled away on non-Linaro work for about half the week.
Dave
Hi,
Android:
* managed to remotely debug a system process (like debuggerd) using
gdbserver
libunwind:
* found an error when unwinding via DWARF debug frames when
configured for REMOTE_ONLY
* discussions on the me revealed that libunwind-ptrace should not be
compiled for REMOTE_ONLY case at all (it was intended for host!=target)
* this means that our current build approach on Android needs to be
changed in the future
Misc:
* internal meetings
Regards
Ken
RAG:
Red:
Amber: upstream-omap3-cleanup stalled, not clear whether we're going
to have any time for it this quarter
Green:
Current Milestones:
|| || Planned || Estimate || Actual ||
||upstream-omap3-cleanup || 2011-11-10 || 2011-11-10 || ||
(Future milestones to be added once post-Connect planning is completed.)
Historical Milestones:
||add-omap3-networking || 2011-10-13 || 2011-10-13 || 2011-10-13 ||
||a15-systemmode-planning || 2011-10-13 || 2011-10-13 || 2011-09-22 ||
||a15-usermode-support || 2011-11-10 || 2011-11-10 || 2011-10-27 ||
== linaro-qemu-11.11 ==
* 2011.11 release: tarball built, tested and released
== other ==
* nailing down A15/KVM work we're going to do this quarter
* usual upstream code review/etc
* sent patches upstream to fix some easy bugs somebody found
running Coverity on QEMU's source code
Hi!
* Ran EEMBC and SPEC on the ursa4. Sorted out a bunch of basic questions
related to permissions ans such with Michael. Familiarized myself with the
scripts for parsing benchmark results.
* Created wiki for running benchmarks in cbuild. It is in my sandbox right
now: https://wiki.linaro.org/AsaSandahl/Sandbox/RunningBenchmark
* Started off SPEC runs for comparing the "train" and "ref" data sets. We
want to know if the changes between variants are the same for the two sets.
Best regards
Åsa
The Linaro Toolchain Working Group is pleased to announce the
release of Linaro QEMU 2011.11.
Linaro QEMU 2011.11 is the latest monthly release of
qemu-linaro. Based off upstream (trunk) QEMU, it includes a
number of ARM-focused bug fixes and enhancements.
New in this month's release:
- The ARM vexpress-a9, versatilepb, versatileab and realview-*
boards now have audio support (thanks to Mathieu Sonet who
contributed a PL041 implementation upstream)
- Support for multiple instances of the "-sd" option on the
command line has been dropped; this was never present in
upstream QEMU and has been removed for consistency. Use
"-drive,if=sd,index=N,file=file.img" for N=0,1,2... instead
- Fixes #886980: 8 and 16 bit reads from the OMAP GPIO module
would crash due to an infinite recursion
- Fixes #823902: problems running multithreaded programs in
linux-user mode
Known issues:
- Graphics do not work for OMAP3 based models (beagle, overo)
with 11.10 Linaro images.
NB: if you run QEMU on a host system without properly configured
audio you might find that QEMU now hangs at some point; you can
fix this by fixing your host system, or work around it by setting
the environment variable QEMU_AUDIO_DRV=none.
If you build from source you may now want to pass configure
a suitable --audio-drv-list=LIST option.
The source tarball is available at:
https://launchpad.net/qemu-linaro/+milestone/2011.11
Binary builds of this qemu-linaro release are being prepared and
will be available shortly for users of Ubuntu. Packages will be in
the linaro-maintainers tools ppa:
https://launchpad.net/~linaro-maintainers/+archive/tools/
More information on Linaro QEMU is available at:
https://launchpad.net/qemu-linaro
Hi,
- SLP improvements for weight-h264-pixels16x16-8 (libav):
- conditions in SLP - committed upstream
- support pattern detection in SLP - implemented
- enhance mixed condition pattern to handle non-constant then/else
clauses - implemented
weight-h264-pixels16x16-8 now gets vectorized with 2.6x speedup.
- Vectorizer maintenance (bug fixes, patch reviews).
I'll be on vacation on Sunday.
Ira
Hi there,
As discussed with Loïc, please find attached my slides to the ELCE presentation related to our implementation of linux-awareness for JTAG debugging. I still need a formal clearance of my organization on my contribution patch, but I (and my managers) will be happy to see some or all of this work benefit to-and-from the community. If you are interested, I will try to upload a self-contained qemu-based demo to a public ftp.
Cheers,
Marc Titinger.
> -----Original Message-----
> From: Loïc Minier [mailto:lool@dooz.org]
> Sent: Wednesday, November 02, 2011 3:19 PM
> To: Marc TITINGER
> Cc: Michael Hope; Ulrich Weigand
> Subject: Re: contribution Linux Kernel Debugger
>
> On Wed, Nov 02, 2011, Marc TITINGER wrote:
> > J'ai été content de vous rencontrer toi et Nicolas à la suite de ma
> > présentation pour discuter de l'opportunité de la contribution de
> > notre debugger linux. J'ai une question: dans la mesure ou STMicro ne
> > fait pas partie des membres de linaro, aurais-je un accès restreint
> > aux outils et discussions si je souhaite contribuer? Quels serons les
> > blueprints correspondant à ce projet ?
>
> Most things Linaro does are public; concerning the toolchain,
> benchmarks are kept private due to licensing constraints. Even if
> STMicro is not a member, you're welcome to present your ideas and code
> to us (we don't mind if STMicro joins as a member though ;-).
>
> We covered topics similar to your ELC-Europe talk this week:
> https://blueprints.launchpad.net/linaro-toolchain-misc/+spec/linaro-
> toolchain-kernel-debugging
>
> Ulrich Weigand and Michael Hope will continue discussions around where
> we will go in terms of helping kernel debugging next cycle, it might
> be
> that we end up working on similar areas than the ones you and I
> discussed (special handling for linux in GDB -- tasks, backtracing
> across kernelspace/userspace; OpenOCD fixes...).
>
> Your slides don't seem to be at
> https://events.linuxfoundation.org/events/embedded-linux-conference-
> europe/titinger
> yet, so perhaps you could share a link with Michael and Ulrich? or
> post on the linaro-toolchain@ mailing-list
>
> We'll be a bit busy this week, but if you want to discuss your
> patches,
> upstreaming, further developments, I would think Michael can arrange
> for you to join a Toolchain WG call in the next weeks -- Michael, I'll
> let you comment once you get to see the slides :-)
>
> --
> Loïc Minier
Summary:
* Add zlib and libiconv support in crosstool-ng and repack embedded
toolchain source package.
Details:
* Read crosstool-ng scripts, configs and document to learn on how it works.
* Try mkedwards's extensions for crosstool-ng at
https://github.com/mkedwards/crosstool-ng. It does have lots of
extensions, the GDB-cross can build. But zlib and libiconv do not meet
our requirement.
* Add config, patch and build scripts for zlib and update the binutils
build scripts to use the prebuilt zlib.
* Add config and build scripts for libiconv and update the build
scripts of gcc and gdb.
* Write scripts to patch and repack embedded toolchain source packages
to the standard format.
Plans:
* Linaro connect: Oct. 31 - Nov. 4.
* Integrate the repack scripts with crosstool-ng.
Thanks!
-Zhenqiang
RAG:
Red:
Amber:
Green:
Current Milestones:
|| || Planned || Estimate || Actual ||
||upstream-omap3-cleanup || 2011-11-10 || 2011-11-10 || ||
Historical Milestones:
||add-omap3-networking || 2011-10-13 || 2011-10-13 || 2011-10-13 ||
||a15-systemmode-planning || 2011-10-13 || 2011-10-13 || 2011-09-22 ||
||a15-usermode-support || 2011-11-10 || 2011-11-10 || 2011-10-27 ||
== other ==
* Linaro Connect week. Included an extremely useful double-length
session about KVM on A15, which should turn into blueprints/plans
in due course
* Found out a bit more about UEFI -- I'm leaning towards having QEMU
for vexpress run UEFI by default as a way of letting you just pass
it a disk image rather than having to feed it a separatekernel/initrd.
(Will look into this more when the ARM landing team have it all
building and working on hardware.)
* I have a working prototype of the QEMU virtio-mmio transport (written
to Pawel's spec). However to get this upstream we will first need to
properly refactor the qemu virtio code so the link between the
transport and the blk/net/etc backends is a qdev bus.
-- PMM
Continue working on the regsiter pressure estimation implementation -
testing the implementation on libav micro benchmarks.
With the patch some SMSed kernels in put-h264-qpel8-hv-lowpass-8,
swscale-rgb24ToY_c mjpegenc benchmarks are identified as having
register pressure.
I'm looking at the kernels which still have regressions with SMS and
it seems the reason is not related to register pressure.
Hi All,
This is a brain dump of what I learned about running LAVA today.
Dave will probably find a place for this in the Validation wiki, but
I'll pass it round in the meantime.
Hope it helps
Andrew
Hi,
* libunwind
* posted small bug fixes
* noticed the unwinding on Android is broken somehow
(need to track down the commit that broke it)
* linaro android
* repo sync fails due invalid bionic commit id (#885792)
* tried to remotely attend the Connect
* +1 for having live streams of the plenaries
(http://video.ubuntu.com/live/)
* -1 for pointing us to the wrong grand sierra irc channels
(http://uds.ubuntu.com/participate/remote)
* icecast streams worked most of the time
(* public holiday on tuesday)
Regards
Ken
=== 64 bit atomics
* I got the race in membase down to a futex issue, and asking dmart
pointed me at a kernel bug that
affects recent kernels where a fix had gone in about a month ago.
That was a nasty one!
* I've still got a few bugs left; most are turning out to be timing
races in the test code (e.g. one that
times out after 2seconds but the code takes around 1.7 seconds ish -
but if something else gets
in trips over the line, and another one where it did a recv_from on a
socket but only got
the start of a message, presumably because the sender had used
multiple sends). It's tricky going
because the tests are a combination of most scripting languages (perl,
python, ruby with a splash of Erlang).
I've so far found no bugs in the atomic code.
* I looked at apr and SDL-1.3; both of which use atomics; but end up
not using 64bit atomics;
the tendency is for them to ensure they can do atomics on long and on
a void*; both of which
for us are 32bit.
=== String routines
* I've got the Newlib A15 optimised memcpy running in a test harness
at the moment for
comparison.
=== Listening to connect
* I listened in to a few connect sessions each day; the 1st day or
so was 3/4 lost on
audio systems that didn't work (I'm especially annoyed at not being
able to hear the QEMU for A15/KVM session
and toolchain support for kernel). The Rypple session was rather lost
through the lack of any screen share
or slides.
Hello all,
I've been playing around with linaro and have it working on my
Pandaboard locally. I have a couple of questions about the linaro
environment; if this is the wrong forum, I'm happy to take it elsewhere.
I see that Linaro makes monthly releases of the hwpacks and images.
How are the packages/binaries in those images created? Are they
cross-compiled, or compiled natively on the target platform? If they
are cross-compiled, how is the environment created?
The reason I ask is that we've been looking at cross-compiling some
packages ourselves, and have been running into issues. So we were
wondering what toolchain the linaro community uses.
Thanks in advance,
--
Chris Lalancette
Hello all,
I've been playing around with linaro and have it working on my
Pandaboard locally. I have a couple of questions about the linaro
environment; if this is the wrong forum, I'm happy to take it elsewhere.
I see that Linaro makes monthly releases of the hwpacks and images.
How are the packages/binaries in those images created? Are they
cross-compiled, or compiled natively on the target platform? If they
are cross-compiled, how is the environment created?
The reason I ask is that we've been looking at cross-compiling some
packages ourselves, and have been running into issues. So we were
wondering what toolchain the linaro community uses.
Thanks in advance,
--
Chris Lalancette
Hi,
- Finished rewriting SLP analysis to support not only unary and binary
operations. Committed upstream.
- Implemented cond_expr support in SLP (for libav weight_h264_pixels).
Testing it now.
- Vectorizer maintenance (test/bug fixes, patch reviews).
Ira
Testing an initial version of the implementation which estimates
register pressure in SMS on libav micro benchmarks.
I see 20% improvements in mjpegenc microbench and 11% on aacsbr-2 with
SMS. However swscale-rgb24ToY_c
still have spills in the final code although it requires maximum 64
VFP_REGS registers out of the available 64 registers so I'm trying to
understand the reason for the spill.
==Progress===
* Off for one day during the week for Diwali.
* Connect preparation - Wrote down areas to look at during connect and
tried to plan what we
want to look at during connect.
* Looked at some of the cases with vcond<float> with Ira and helped
frame blueprint.
* Investigated one of the big performance regressions in the popular
embedded benchmark
and looked at why it wasn't being vectorized only to realize that it
couldn't be. Thanks
Ira. Still don't know why ARM state is 22% faster than Thumb2 state.
* Looked at the issue with fPIC where GCSE appears to remove a label
for sometime
but not much progress.
=== Plans ===
* Connect ! next week and then vacation.
Absences.
* 26 Oct - Diwali
* 31st Oct - 4th Nov - Linaro Summit Orlando - Travel booked -
* 08 Nov - 11 Nov - Vacation booked
* Dec 19 - 31st Dec - Vacation booked
== 64 bit atomics ==
* I've been building and testing membase
* Version 1.7.1.1 source builds OK (after turning off -Werror due to
some of their curious type naming)
* The git version fails to build - it doesn't seem consistent
* 1.7.1.1 passes simple tests, but there are 3 tests in its test
suite that intermittently fail on ARM and
seem to be solid on x86. (There are also some that just require
timeouts increased due to the
relatively slow machine).
* t/issue_163.t turned out to be a timing race in the test itself,
made worse by being on a relatively slow
machine and probably made worse by the Pandas odd idea of timing.
That was reported to them with
a break down of it, and upstream has fixed their test. (
http://code.google.com/p/memcached/issues/detail?id=230 )
* t/issue_67.t is proving tougher; once in a while memcached will
lock up during init in thread_init;
there is one particular point where adding a printf will make it work
apparently reliably. I've got one
or two ideas but I need to check my understanding of pthread_cond_wait first.
* There is an assert I've seen triggered once - not looked at that yet.
== String routines ==
* While I was off last week, my memchr and strlen were accepted into newlib
* Joseph has responded to my eglibc mail, with a couple of small queries.
== Other ==
* Wrote a more detailed test case for bug 873453 (odd timing
behaviour on panda); it's
quite odd - I can get > ~80ms timing discrepency so it's not a clock
granularity issue.
* Replicated a QEMU crash for Peter.
Dave
Hi,
* finished changing libunwind to be more portable
* tested patchset on ARM and X86_64
* now builds on Android without modifications
(Android.mk, config.h and libunwind-common.h are still required)
* verified that the modified debuggerd still works
* discussed backtracing using libunwind on ARM with Harald from the BSC
* they use libunwind in a sampling tool that generates Paraver
tracefiles
* started to upgrade my Linaro Android environment and ran into issues
* need to check:
* why building the toolchain using linaro-build.sh fails
* why repo sync fails due to invalid platform/bionic SHA1
* what happened to LEB-panda.xml
Regards
Ken
RAG:
Red:
Amber:
Green:
Current Milestones:
|| || Planned || Estimate || Actual ||
||a15-usermode-support || 2011-11-10 || 2011-11-10 || 2011-10-27 ||
||upstream-omap3-cleanup || 2011-11-10 || 2011-11-10 || ||
Historical Milestones:
||qemu-linaro-2011-07 || 2011-07-21 || 2011-07-21 || 2011-07-21 ||
||qemu-linaro 2011-08 || 2011-08-18 || 2011-08-18 || 2011-08-18 ||
||qemu-linaro 2011-09 || 2011-09-15 || 2011-09-15 || 2011-09-15 ||
||add-omap3-networking || 2011-10-13 || 2011-10-13 || 2011-10-13 ||
||a15-systemmode-planning || 2011-10-13 || 2011-10-13 || 2011-09-22 ||
== a15-usermode-support ==
* A15 instruction support patches committed upstream in time for
upstream's 1.0 release
== upstream-omap3-cleanup ==
* some work on restructuring the omap3 patchset -- it's now basically
in the right order and the last 'touches several different
bits of code' jumbo patch has been split
== other ==
* sent some patches upstream which address the main things I
want to get into qemu 1.0 (PL041 audio support and fixing a
regression in handling multithreaded programs in linux-user mode)
* A15 KVM planning work and other preparation for Linaro Connect
* finally tracked down the qemu-on-ARM memory corruption: we
mmap the code generation buffer at 0x1000000 with MAP_FIXED;
unfortunately this is now in the middle of glibc's heap...
(filed as LP:883133)
* qemu now has a coroutine implementation which defaults to using
makecontext() if it is present. Unfortunately ARM eglibc provides
an implementation which always returns ENOSYS, which is a bit
tricky to detect with a compile time configure check (without
breaking cross-compilation support).
* these two things (and some other known bugs) mean that QEMU on
ARM hosts is basically broken, and will probably continue to be
since we don't have the spare resource to test and fix bugs
(beyond those which we need to fix for KVM-on-ARM)
* Looked at how to configure Firefox and how to build different parts of the
program. Usage of .mozconfig, myrules.mk and myconfig.mk.
* Tested the Talos framework. https://wiki.mozilla.org/Buildbot/Talos. I
think it would be good to use Talos for the browsing benchmarks. We can
discuss it further at connect.
* Preparing for connect.
Best Regards
Åsa
Summary:
* Exercise crosstool-ng and summarize the gaps.
Details:
* Exercise crosstool-ng
(1) Sync with lp:~linaro-toolchain-dev/crosstool-ng/linaro.
(2) Try to config linux-host-baremental-target an
mingw32-host-baremental-target.
(3) Try to build the toolchain for both embedded toolchain and
linaro-gcc-4.6-2011.10 with the config.
. C compiler for linux and mingw32 hosts and c++ compiler for
linux host can be built without any change.
. C++ compiler for mingw32 host can be built after PCH is disabled.
. GDB-cross build fail due to dependence packages.
* Gaps in crosstool-ng
(1) Improve GDB-cross scripts to download and build the dependence
packages: expat and ncurses. Or put expat and ncurses as
companion_libraries.
(2) To remove dependence, embedded toolchain requires more
prerequisites like zlib.
New config and scripts are required to support the packages.
(3) Currently, the embedded toolchain source packages are released
as a tarball, which includes gcc, gmp, etc. New scripts are required
to support it.
(4) To make sure the toolchain can run with lower version glibc like
redhat4/5, the embedded toolchain requires lower version native
gcc4.3.6 to build it.
To support it,
. Users can build the native gcc manually, or
. Enhance the scripts to add one step to build native gcc.
(5) All the default package configurations are different from
embedded toolchain internal build scripts.
Since the configurations in embedded toolchain had been tuned
and tested, we will change the configurations in crosstool-ng if they
do not match and not configurable.
The same rule will apply for linaro toolchain.
Plans:
* Write scripts to re-pack the embedded toolchain source packages.
* Add the supports for all prerequisites in crosstool-ng menuconfig.
Thanks!
-Zhenqiang
