Hi,
I have started to use the new cpuidle tracepoint and created a plugin
for pytimechart.
I'm not sure if it's the right way to add this cpuidle trace format
update but it's the less intrusive one.
I also have a plugin for new cpu_hotplug trace points but i'm waiting
for trace approval before sending it
Vincent
Subject: [PATCH 1/1] cpuidle: new plugin
new tracepoints are available for cpuidle
Signed-off-by: Vincent Guittot <vincent.guittot(a)linaro.org>
---
timechart/plugins/cpuidle.py | 35 +++++++++++++++++++++++++++++++++++
1 files changed, 35 insertions(+), 0 deletions(-)
create mode 100644 timechart/plugins/cpuidle.py
diff --git a/timechart/plugins/cpuidle.py b/timechart/plugins/cpuidle.py
new file mode 100644
index 0000000..32dce91
--- /dev/null
+++ b/timechart/plugins/cpuidle.py
@@ -0,0 +1,35 @@
+from timechart.plugin import *
+from timechart import colors
+from timechart.model import tcProcess, c_state_table
+
+class cpu_idle(plugin):
+ additional_colors = """
+"""
+ additional_ftrace_parsers = [
+ ('cpu_idle', 'state=%d cpu_id=%d', 'state', 'cpuid'),
+ ]
+
+ additional_process_types = {
+ }
+
+ @staticmethod
+ def do_event_cpu_idle(self,event):
+ self.ensure_cpu_allocated(event.cpuid)
+ tc = self.tmp_c_states[event.cpuid]
+ if event.state != 4294967295 :
+ if len(tc['start_ts'])>len(tc['end_ts']):
+ tc['end_ts'].append(event.timestamp)
+ self.missed_power_end +=1
+ if self.missed_power_end < 10:
+ print "warning: missed cpu_idle end"
+ if self.missed_power_end == 10:
+ print "warning: missed cpu_idle end: wont warn anymore!"
+ tc['start_ts'].append(event.timestamp)
+ tc['types'].append(colors.get_color_id(c_state_table[int(event.state)]))
+ tc['linenumbers'].append(event.linenumber)
+ else :
+ if len(tc['start_ts'])>len(tc['end_ts']):
+ tc['end_ts'].append(event.timestamp)
+
+plugin_register(cpu_idle)
+
--
1.7.1
Nicolas,
With the patch:
ARM: 6746/1: remove the 4x expansion presumption while decompressing the kernel
I get a build error. This is when building my packaged kernel with
debuild. Notice the stat failure __after__ the "Kernel:
arch/arm/boot/Image is ready message". Then later ld fails because of
the stat failure.
GEN .version
CHK include/generated/compile.h
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
stat: cannot stat `arch/arm/boot/compressed/../Image': No such file or directory
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gzip
CC arch/arm/boot/compressed/misc.o
CC arch/arm/boot/compressed/decompress.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
AS arch/arm/boot/compressed/piggy.gzip.o
LD arch/arm/boot/compressed/vmlinux
arm-linux-gnueabi-ld:--defsym _image_size=: syntax error
The odd thing is that after the failure I can look in the directory
and Image is there so its like it some kind of race?
For the moment I am working around this be reverting this patch but
obviously thats not a real solution.
Thanks,
John
Hi,
The notes and actions for this weeks Android Platform Team meeting along
with team activity reports are now available at:
https://wiki.linaro.org/Platform/Android/Meetings/2011-03-02
= Actions Recorded =
* JamieBennett to see if we can allocate a Panda board for jstultz
* patrikryd to back out battery support from the
android/platform/frameworks tree
* jeremychang and jserv-- to investigate why pandroid platform breaks
with fbdev
* patrikryd to confirm
https://android-build.linaro.org/job/android-u8500href/ tarballs
work and fix if necessary
* JamieBennett to update meeting template for new format
* Team to summarise what they are doing on
http://wiki.linaro.org/Platform/Android/CurrentProjects and try to
derive Blueprints from that
* johncylee and asac to talk about merging his content into
requirements
* everyone to review requirements document and check if there is
anthing we can better define
* JamieBennett to talk to jstultz how the oesf team goes
Regards,
Jamie.
--
Linaro Release Manager | Platform Project Manager
Hi,
The weekly Linaro Release Meeting will be held at 17:00 UTC tomorrow.
The agenda for the meeting can be found at:
https://wiki.linaro.org/Releases/WeeklyReleaseMeeting/2011-03-03
and previous action items were:
* nytowl to test s5pv310 hwpack and images
* slangasek to raise the issue with debian-policy on whether or not we
need e2fsprogs as Essential: yes
* JamieBennett to invite nytowl to the release meeting
* tgall_foo to email JamieBennett, slangasek about netbook image status
If you have points to raise or bugs that need to be discussed please add
them to the wiki page above.
Regards,
Jamie.
--
Linaro Release Manager | Platform Project Manager
Hi All,
Keep your diaries free!
The dates for our remaining 2011 summits and sprints are as follows:
- May 9 - 13: Linaro @UDS Developer
Summit<https://wiki.linaro.org/Events/2011-05-LDS>,
Budapest Hungary
- August 1 - 5: Linaro 11.11 Mid Cycle
Sprint<https://wiki.linaro.org/Events/2011-08-LDS>,
Cambridge UK
- October 24 - 28: Linaro @UDS Developer
Summit<https://wiki.linaro.org/Events/2011-10-LDS>,
Orlando Florida
The Events page has been updated accordingly:
https://wiki.linaro.org/Events/
And for people in Linaro, the Linaro Events calendar has been updated with
the meetings, so you can add them to your calendars if you want.
--
Thx
Stephen Doel
Linaro Ltd
Chief Operating Officer
+44 77 66 014 247
Hi,
Just tested the imx51 Thumb-2 kernel on efikamx here -- it boots fine,
but we only went as far as the initramfs.
Is anyone currently relying on CONFIG_LATENCYTOP? If so, we should
investigate what the incompatibility is...
Cheers
---Dave
On Wed, Feb 23, 2011 at 6:11 PM, Dave Martin <dave.martin(a)linaro.org> wrote:
> Hi there,
>
> Talking with Loic just now, we thought it could be worth turning on
> Thumb-2 in the main omap kernel package after all, since we've at
> least seen it work on a few different boards now. It feels ready for
> wider testing.
>
> Is it possible for you to move to a newer snapshot of the 2.6.38
> linaro tree, or will that be problematic at this stage?
>
>
> Since the imx51 kernel at least seems to build and boot in Thumb, it
> could be worth enabling a separate build in a PPA, but it's may not
> mature enough for everyone to use as the main kernel just yet. If you
> want to try this, you need CONFIG_ARM_UNWIND=y, CONFIG_LATENCYTOP=n
> and CONFIG_THUMB2_KERNEL=y
>
> Cheers
> ---Dave
>
Hi. On snapshots.linaro.org/11.05-daily/ there are now the
following different kinds of snapshot image:
linaro-alip/
linaro-developer/
linaro-graphical-engineering/
linaro-handset-plasma/
linaro-headless/
linaro-multimedia-engineering/
linaro-nano/
linaro-netbook-efl/
...but I can't find anything on the wiki which documents
what each of these images is actually for, which makes it
hard to know which one to choose.
https://wiki.linaro.org/Releases/DailyBuilds
suggests using linaro-headless, but that doesn't seem
to have built since the 18th February. Mail to this list
on the 8th Feb said:
> Please note that the headless and netbook-efl images
> will be replaced by the Nano and Evaluation Ubuntu
> Desktop builds soon
but there hasn't been an official announcement that this
happened -- is linaro-headless now gone, or has it just
failed to build for the past fortnight?
(If it has been obsoleted, how about a readme in
11.05-daily/linaro-headless/ saying "try $elsewhere
instead" ?)
thanks
-- PMM
Hi,
You can see them at
https://wiki.linaro.org/Platform/Infrastructure/Meetings/2011-03-01
or below.
Thanks,
James
=== Attendees ===
* Mattias Backman
* Guilherme Salgado
* Deepti Kalakeri
* James Westby
* Jamie Bennett
* Alexander Sack
=== Agenda ===
* Actions from last meeting
* Team status
* Reporting days
* AOB
=== Action Items ===
* james_w to co-ordinate deployment of salgado's patchwork tree in his absence
* james_w to email salgado about patch metrics
* james_w to get deepti a machine to host jenkins
* mabac to request reviews for some svammel changes, and review some code from other team members
* salgado to send deployment docs to the patchwork RT ticket when ready
* james_w to request status reports on Monday
=== Action Items from previous meeting ===
* James to Cc Guilherme on RT for patchwork: DONE
* James to email Guilherme with info on patches(a)linaro.org account: DONE
=== Minutes ===
* Team status reports
* Deepti Kalakeri
* Got hudson/jenkins build and tests of linaro-gcc on her local instance
* Needs access to a hosted instance to make the work public and have it run reliably.
* Mattias Backman
* Project created for BuildFailureBugFiling: https://launchpad.net/svammel. Good progress on the implementation.
* Will create a blueprint for tracking the work
* Will be refactoring to add more unit tests, and add more of the features requested by Steve.
* Will also request some reviews from others for some of the changes, and will also review other people's code in other projects.
* Guilherme Salgado
* Good progress on PatchTracking. Using stgit to manage the patches he has on top of patchwork.
* Got some more positive upstream feedback on patchwork patches.
* Some patches are still awaiting review though, and most have not actually been merged despite favourable review.
* Away for most of 10 days after this week. James will co-ordinate getting a patchwork instance in his absence. There is nothing urgent that should be handled in his absence, but patch tracking implementation will pause for a while.
* Has written some further documentation on deployment, which he will put in the RT ticket to aid IS.
* James will send information that he has on the metrics that management want to see this month.
* James Westby
* Continued excellent response to status.linaro.org. Most urgent requests are dealt with, one still in review. Hopefully the project can be put in to maintainence soon, until the next round of improvements are scheduled.
* Reporting days
* It has been requested that we include our individual weekly reports in the meeting notes, and have them prepared before the meeting for discussion.
* With the timing of our meeting this is a few days before the team status report on Thursday. It's not a big issue to have slightly stale information for that, but it may be that we want to change the day of our meeting anyway.
* Nobody had any problem with the day of the meeting, so we will keep that as it is, and send in status reports before the meeting. James will send reminders appropriately from next week on.
Forwarded for interest; a number of ARM / Linaro folks were involved
last week.
----- Forwarded message from Hector Oron <zumbi(a)debian.org> -----
From: Hector Oron <zumbi(a)debian.org>
Date: Tue, 1 Mar 2011 11:03:02 +0000
To: debian-devel-announce(a)lists.debian.org
Cc: bbrv(a)genesi-usa.com, david(a)toby-churchill.com
Reply-To: debian-embedded(a)lists.debian.org
Subject: Bits from ARM and Embedded Sprint
Mail-Followup-To: debian-devel(a)lists.debian.org
Hello,
During the Debian ARM and Embedded Sprint, we had the opportunity to discuss
and work on the following areas:
ARM ports
---------
* 'armel'
Several FTBFS RC bugs were fixed.
* 'armhf' [0]
Debian package management system (dpkg) assumes that a new ABI is a new Debian
architecture, and that there is a one-to-one mapping between Debian architectures
and triplet names. Upstream GNU tools assume that 'armel' and 'armhf' share the
same GNU triplet. That would make armhf and armel the first Debian architectures
which shared a triplet.
There are several proposals to fix this problem:
* Modify upstream GNU GCC triplets to allow different triplets per ABI
* Introduce a new tuple naming scheme, as detailed in multiarch proposal and
use it as the canonical name in dpkg
We had the opportunity to discuss with GCC upstream engineer (Ramana) about our
distribution problem. The problem was posted to the GCC mailing list [1] and it
looks like there are no major objections against it. A new triplet name might be
adopted for Debian 'armhf', likely to be arm-linux-gnueabi_hf, but discussion it
is still going on between `dpkg' maintainers and GCC upstream folks.
Several NMU uploads were done into the archive adding support for armhf [3].
* Thumb-2 Kernel
Some progress on kernels built in Thumb-2 (continuing Linaro work).
Thumb-2 kernel now seen to boot on efikamx and Freescale mx51evk boards, as
well as OMAP3/4.
[0] http://wiki.debian.org/ArmHardFloatPort
[1] http://gcc.gnu.org/ml/gcc/2011-02/msg00408.html
[2] http://lists.debian.org/debian-devel/2011/02/msg00351.html
[3] http://wiki.debian.org/ArmHardFloatTodo
Please direct any queries about ARM ports to: debian-arm(a)lists.debian.org
Multiarch [0][1][2]
-------------------
* MultiarchCross Wiki page [3] was updated to reflect current status and describe
the creation of a new patch for pkg-config [4] which implements the --host option
described by upstream.
* A phone conference with Steve Lanagsek, Rafael Hertzog and Loic Minier attending
was held to get the team, and ARM engineers, up to speed on Multiarch and the armhf
triplet/tuple naming issue.
* A possible patch for debhelper [5] was created to implement DEB_HOST_MULTIARCH
substitution support in install files. This allows libraries, header files, symlinks
and binaries to be relocated into multiarch-compatible paths when building the package,
using a value passed from dpkg-architecture. A variable needs to be added into
the install location in each install file, together with a small change debian/rules.
Simple tests indicated that ${DEB_HOST_MULTIARCH} should be a suitable placeholder
for the substitution. The change probably needs to be part of a new debhelper
compatibility - compat 9. Packages which do not currently use debhelper would
need to use sed or equivalents to perform the substitution.
* Test packages for this method have been hosted as patches in Emdebian SVN [6],
including the patched version of debhelper, possible patch for gcc-4.5 (via armhf
port development), the patched version of pkg-config and patches for popt and
pcre3. Certain packages are also hosted in an experimental repository [7].
e.g. debian/tmp/usr/lib/libpopt.so.*
lib/ changes to debian/tmp/usr/libx/${DEB_HOST_MULTIARCH}/libpopt.so.*
lib/${DEB_HOST_MULTIARCH}. Binary packages built using this method are available
but ONLY for use within chroots [9]. Please read the README [10] before trying
to use these binaries, it is very easy to completely break your system with the
current test packages. (It is, for example, completely non-trivial to remove
Multi-Arch packages of a foreign architecture which have been force-installed.)
* Some of the notes taken during the meeting can be reviewed at Debian wiki site [8].
[0] http://wiki.debian.org/Multiarch
[1] https://wiki.ubuntu.com/MultiarchSpec
[2] http://wiki.debian.org/Multiarch/LibraryPathOverview
[3] https://wiki.ubuntu.com/MultiarchCross
[4] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=217902#28
[5] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614731
[6] http://www.emdebian.org/trac/browser/current/multiarch
[7] http://ftp.uk.debian.org/emdebian-multiarch/
[8] http://wiki.debian.org/MultiarchEmdebianSprint2011
[9] http://ftp.uk.debian.org/emdebian-multiarch/
[10] http://www.emdebian.org/trac/browser/current/multiarch/README
Please direct any query about Multi-Arch to: debian-dpkg(a)lists.debian.org
Bootstrapping a.k.a. Cyclic dependencies issues
-----------------------------------------------
* A discussion session was held to explain the current bootstrapping issues and
proposals. There was lively discussion and lots of good feedback on mechanism
plus ideas on how to develop it into a qa service. Notes of the discussion are
here [4]
* A Debian Bootstrap wiki page has been updated to prepare a specification for
work on breaking cyclic build-dependency loops [0], and making Debian
auto-bootstrappable.
* Patches were created for (debian versions of) poppler, gtk+2.0 and qt4-x11 [1],
and (natty versions of) krb5, poppler, cyrus-sasl, and openldap [2] to implement
Bootstrap dependency support to break circular dependencies when bootstrapping
new and existing architectures. Support is implemented using an environment variable:
DEB_BOOTSTRAP=1. The patches use the existing upstream support in the relevant
packages to turn off functionality and then disable certain binary packages from
being built, so that the temporary bootstrap build can be built without the full
set of build dependencies. The smaller set of build-dependencies is defined in
debian/control as Build-Depends-BootstrapN. Later bootstraps can turn on more of
the functionality until the final build restores the original Debian configuration.
Bootstrap packages are made available to the build process only, via temporary
repositories. All reverse dependencies which managed to build against the bootstrap
packages are rebuilt against the final version before being uploaded to the full
archive. Packages which failed to build against the bootstrap are built against
the full version of the dependency. Typical changes include disabling LDAP
support, turning off CUPS support etc.
Patches are in Emdebian SVN and in Launchpad PPA / bazaar branches
* patch for natty version of dpkg, to
1) make dpkg-checkbuildeps use Build-Depends-BootstrapN when --bootstrap=N is
passed.
2) make dpkg-buildpackage pass --bootstrap=N when env var DEB_BOOTSTRAP=N is
set.
* Alternate patch implementing the scheme using DEB_BUILD_OPTS 'bootstrap=N',
instead of DEB_BOOTSTRAP=N
* Circular bootstrap loops were identified using xdeb [3], which also got improved
when some loops were identified as false positives. The new design aims to prevent
false loops being identified by considering only binary build-deps that are
actually needed, not all the binaries built by a particular source package. This
means that the existing analysis of all 900 packages in maverick base will need
to be re-run to get a more realistic picture.
* xdeb is gaining logic for setting DEB_BOOTSTRAP=N when a bootstrap option is
available.
* Work on getting the same version of xdeb into Debian and Ubuntu was done.
[0] http://wiki.debian.org/DebianBootstrap
[1] http://www.emdebian.org/trac/browser/current/bootstrap
[2] https://code.launchpad.net/~peter-pearse
[3] http://emdebian.org/bootstrap/examples/
[4] http://wiki.debian.org/DebianBootstrap/EmdebianSprint2011
Please direct any queries about bootstrapping to: debian-embedded(a)lists.debian.org
FreedomBox
----------
* A presentation on Freedom Box was made during the sprint [0]
* `Boxer' [1] is a framework to generate optimized images for Freedom Box project
as well as encouraging flexible hacking for developers was started during the
sprint. Boxer contains a list of Debian packages split by sections (at the moment
debug, httpd-apache, httpd-lua, ipv4ll, webchat, xmpp-erlang, xmpp-lua) which can
be enabled and disabled at wish. It is planned to add preseed information as well,
so packages can be tuned to fit Freedom Box requirements in a generic way. Boxer
generates the metadata to be fed into other tools. For example, there are already
hooks acting as git submodules into `live-build' and `multistrap', and potentially
more hooks could be created to support other frameworks.
* Hand drawn drafts for visualizing "The stream of Debian software development"
were done and eventually those might be published at freedombox-discuss mailing
list.
* Other random hacking on sd-installer (a tool to ease Debian installation into
SD/MMC cards) happen.
* Some research for Freedombox User Interface was also done.
[0] http://dr.jones.dk/emdebian/fb/
[1] http://git.emdebian.org/?p=upstream/boxer.git;a=blob;f=README
Please direct any queries about FreedomBox to: freedombox-discuss(a)lists.alioth.debian.org
Flash-kernel
------------
A discussion was held on flash-kernel's issues, the main issues being scalability
to more and more boards, and usage of board-specific data across tools. Various
affected tools were brought up and the proposed improvements to flash-kernel were
discussed, as well as some WIP cleanups [1]. The most important outcome is that
the board data should be split out of flash-kernel entirely and carefully versioned.
The project's wiki page [2] was updated to match the discussion.
[1] http://git.debian.org/?p=users/lool/d-i/flash-kernel.git
[2] http://wiki.debian.org/FlashKernelRework
Please direct any query about flash kernels to: debian-arm(a)lists.debian.org
Cross toolchain support
-----------------------
A group was created on alioth [1] to improve cross toolchain support within Debian
merging efforts from both Emdebian and Linaro packages, some notes were taken
during discussion now summarized in a wiki site [2]. In sumary it was decided to
upload something along the lines of the armel cross-toolchain that was in Ubuntu
maverick for the time being, until a cleaner solution can be acheived once
cross-architecture dependencies are introduced via Multiarch.
[1] https://alioth.debian.org/projects/crosstoolchain/
[2] http://wiki.debian.org/ToolChain/Cross
Please direct any queries about cross toolchain support to: debian-embedded(a)lists.debian.org
The power of grouping and teaming up
------------------------------------
We had the opportunity to watch a documentary by Sugata Mitra: 'The child-driven
education' [0], which shows a bunch of experiments done in children education
environment and showing that they perform much better when they team up. We
would like to share the link to it.
[0] http://www.ted.com/talks/lang/eng/sugata_mitra_the_child_driven_education.h…
References
----------
* http://wiki.debian.org/Sprints/2011/EmdebianSprint
Thanks to
---------
All the attendees being physically at the Sprint Venue, all the remote attendees
via phone or IRC, nice people working at ARM offices, all the wider Debian
community and sponsors collaborating with the event.
Sponsors
--------
* ARM - http://www.arm.com/ - providing hacking room space and lunch.
* Genesi USA - http://www.genesi-usa.com/ - providing dinner for attendees
* Toby Churchill Ltd - http://www.toby-churchill.com/ - providing dinner for attendees
* Debian - http://www.debian.org/ - providing coolest operative system to hack on
We would also like to thank the above companies for letting their employees being
part of the Sprint, as well as Linaro, Canonical, hands.com, dr.jones.dk, and simtec.co.uk.
The sprint worked really well, with lots of input from a good range of people,
with cross-pollination between people's interests, and plenty of concrete outputs
in the form of useful patches and repositories. The balance between hacking an
discussion worked well. ARM's facilities worked really well. Hopefuly we will be
able to run another similar event in the not too distant future.
List of Participants
--------------------
Hector Oron
Neil Williams
Nick Bane
Wookey
Konstantinos Margaritis
SteveMcIntyre
Philip Hands
Daniel Silverstone
Dave Martin
Oliver Grawert
Jonas Smedegaard
David Rusling
Marcin Juszkiewicz
Loïc Minier
Jonathan Austin
Peter Pearse
Jesse Barker
... and random ARM hackers and visitors: Ramana Radhakrishnan, Leif Lindholm,
Javi Merino, Colin Tuckley, Anna Valiente, Siri Reiter, Steve Wiseman, ..
--
Héctor Orón
"Our Sun unleashes tremendous flares expelling hot gas into the Solar System,
which one day will disconnect us."
-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html
----- End forwarded message -----
--
Steve McIntyre, Cambridge, UK. steve(a)einval.com
You lock the door
And throw away the key
There's someone in my head but it's not me
