From: srinivas <srinivas.kalaga(a)arm.com>
The following patches add power events in /debug/tracing/events/power.
These patches have been tested and applied only on the latest OMAP pm branch. The first diff set is for cpufreq and second one for cpuidle framework.
The first diff patch applies only if OPP layer is included in the OMAP kernel.
Review comments are welcome.
srinivas (1):
Ftrace: Timestamp of entry into low power states and performance
states
arch/arm/plat-omap/cpu-omap.c | 2 ++
drivers/cpuidle/cpuidle.c | 3 ++-
2 files changed, 4 insertions(+), 1 deletions(-)
I'd like to record the running of a typical program such as Firefox,
GCC, or ffmpeg and capture the calls and arguments to functions like
strcpy() and memcpy(). The idea is to generate a usage profile so we
can tell what standard library functions and what variants (i.e.
aligned/unaligned, small copy/large copy) to attack first.
Does anyone know of existing research with this information, or
existing tools that could capture it?
My fallback is to use a LD_PRELOAD trick to replace the interesting
functions with tracing versions.
-- Michael
Hi,
As a followup to a conversation I had with Alexander (asac) on IRC, i'd like
to request the addition of some packages to the headless image. This is to
make the images more useful out-of-the-box.
- ifplugd (dhcp networking)
- screen (multiple terminals over a serial console)
- vim (or any other more complete editor than the vi that ships with busybox)
- openssh (atleast server)
More useful tools to consider (but might be more insteresting only to kernel devs)
- lsusb
- latencytop
- input-utils
- iotop
Regards,
Amit
FYI (CCed Chris if you have questions)
----- Forwarded message from Christopher James Halse Rogers <raof(a)ubuntu.com> -----
From: Christopher James Halse Rogers <raof(a)ubuntu.com>
To: ubuntu-devel-discuss <ubuntu-devel-discuss(a)lists.ubuntu.com>,
ubuntu-devel-announce(a)lists.ubuntu.com,
ubuntu-x <ubuntu-x(a)lists.ubuntu.com>
Subject: Xserver 1.9 transition
X-Spam-Status: No, score=-2.6 required=0.8 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
Summary for the impatient:
********************************************************************
A new X server is soon to be uploaded which requires all the
drivers to be rebuilt. Be careful when upgrading in the next few
days.
********************************************************************
As promised earlier in the cycle, we've got the second X server
transition coming up. This will take us to X server 1.9, which features
improvements to startup time, some memory usage improvements, and many
DRI2 fixes.
The 1.9 server has a new input and video ABI which means existing driver
packages will break.
The server needs to be uploaded first so the new drivers build against
the correct ABI, which means that there will be a period where safe
upgrades will have held-back packages. The dependencies should ensure
that you won't accidentally get a non-working combination of X server
and drivers, but be careful if an upgrade wants to remove X packages.
Happy testing!
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss(a)lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
----- End forwarded message -----
- Alexander
cc'ing linaro-dev
On Fri, Aug 6, 2010 at 10:59 AM, Amit Arora <amit.arora(a)linaro.org> wrote:
> On Fri, Aug 6, 2010 at 1:14 PM, Yong Shen <yong.shen(a)linaro.org> wrote:
>> Hi Amit,
>>
>> Clearly, we did not implement these nodes. See below.
>> root@freescale ~$ cat
>> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
>> cat: can't open
>> '/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies': No
>> such file or directory
>> root@freescale ~$ ls /sys/devices/system/cpu/cpu0/cpuidle
>> ls: /sys/devices/system/cpu/cpu0/cpuidle: No such file or directory
>
> Ok. How about contents of cpufreq/scaling_min_freq,
> cpufreq/scaling_cur_freq and cpufreq/scaling_max_freq ?
>
> Sorry for troubling you on this. But, actually, sending a tarball of
> /sys/devices/system/cpu would have avoided all these questions. :)
>
>
>> About "Error opening terminal: vt100", I still have it. I believe I had
>> already installed ncurse-bin package, since it was compiled with ncursesw
>> togather. This error is printed by ncurses/base/lib_initscr.c. Still
>> checking.
>
Yong, could you set your evironment variables TERM=linux and see if
this error still occurs?
/Amit
Hi,
According to the schedule [1] the Linaro Feature Freeze will be in effect from 2010-08-12, i.e. Thursday. This signals our transition from adding new features to bug fixing and improving what is already there. Exceptions to this process will have to be approved by the release management team [2] using the Feature Freeze exception process [3]. After this date your new features are not guaranteed to be in the next release so please try to get your enhancements in as soon as possible. For an explanation of the Feature Freeze process please see the wiki [4].
Regards,
Jamie.
--
Linaro Release Manager
[1] https://wiki.linaro.org/Releases/1011#Linaro10.11Schedule
[2] https://edge.launchpad.net/~linaro-release
[3] https://wiki.linaro.org/Releases/FreezeExceptionProcess
[4] https://wiki.linaro.org/Releases/FeatureFreeze
-------- Original Message --------
Subject: [ubuntu/maverick] linux-linaro 2.6.35-1000.3 (Accepted)
Date: Fri, 06 Aug 2010 20:01:32 -0000
From: Ubuntu Installer <archive(a)ubuntu.com>
Reply-To: Ubuntu Installer <archive(a)ubuntu.com>
To: Tim Gardner <tim.gardner(a)canonical.com>
linux-linaro (2.6.35-1000.3) maverick; urgency=low
[ John Rigby ]
* LINARO: cleanup debian.linaro control file
Date: Tue, 03 Aug 2010 10:16:29 -0600
Changed-By: John Rigby <john.rigby(a)linaro.org>
Maintainer: Ubuntu Kernel Team <kernel-team(a)lists.ubuntu.com>
Signed-By: Tim Gardner <tim.gardner(a)canonical.com>
https://launchpad.net/ubuntu/maverick/+source/linux-linaro/2.6.35-1000.3
==
Announcing to maverick-changes(a)lists.ubuntu.com
Thank you for your contribution to Ubuntu.
--
You are receiving this email because you are the uploader, maintainer or
signer of the above package.
Morning all. Peter Maydell from ARM has just joined Toolchain WG and
will initially be working on QEMU. As part of that I'd like him to
make a QEMU/Kernel/Distribution combination that makes our lives
easier - something that replaces the limited memory, obsolete hardware
ARM versatile kernel that we use at the moment and that can be used
for a development, buildd, and debootstrap host. This cuts across all
of our groups as it needs kernel input, will be done by toolchain, and
hopefully consumed by user platforms.
A blueprint is available at:
https://blueprints.launchpad.net/qemu-linaro/+spec/qemu-focused-kernel
Feedback would be appreciated,
-- Michael
Hi,
Well, it's that time again, please all welcome Linaro Alpha 3 into the
world. This will be the final release before the beta version arrives
at the end of August and signals Linaro's continued maturity towards
the final November image.
Highlights of this release include:
* A small Linaro headless image with basic OMAP3 beagle board support
(reported working on other architectures with minimal changes).
* A new software archive rebuild with GCC 4.4.4, CodeSourcery
enhancements and ARM-related improvements.
* Support for opengl ES development through MESA.
* GPS support via gypsy and geoclue.
* Netbook user interface capabilities with the latest EFL software
stack.
More Information on this development release as well as download and
installation instructions can be found at:
http://wiki.linaro.org/Releases/1011/Alpha3
More information on Linaro in general and the 10.11 plans can be found
at:
* Homepage: http://www.linaro.org
* Wiki: http://wiki.linaro.org
* 10.11: http://wiki.linaro.org/Releases/1011
Also subscribe to the important Linaro mailing lists and join our IRC
channels to stay on top of Linaro developments:
* Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce
* Development: http://lists.linaro.org/mailman/listinfo/linaro-dev
* IRC: #linaro on irc.freenode.net
For any errata issues please see:
http://wiki.linaro.org/Releases/1011/Alpha3#Issues
Bug reports for this release should be filed in Launchpad against the
individual packages that are affected, if a suitable package cannot be
identified, please feel free to assign them to:
http://www.launchpad.net/linaro
Regards,
Jamie.
--
Linaro Release Manager