From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] Make dyntick work again
Date: Fri, 12 Oct 2007 13:22:18 -0700 [thread overview]
Message-ID: <20071012202218.GH7979@atomide.com> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D9130274290231FFA1@dlee13.ent.ti.com>
* Woodruff, Richard <r-woodruff2@ti.com> [071012 13:16]:
> Hi,
>
> > Time to try powertop on omap!
>
> Here is powertop running on 3430 using dynamic tick :) It would be nice to format the C state information such that it reports residency. Sometime in the future. It is directly useable for seeing timers. Not so many timers running on a full up NFS mounted system. It used to run fine on OMAP2 from GIT once clocksource came.
>
> --------------------
> < Detailed C-state information is only available on Mobile CPUs (laptops) >
>
> Wakeups-from-idle per second : 13.1 interval: 10.0s
>
>
> Top causes for wakeups:
> 38.9% ( 4.2) <interrupt> : 32KHz timer
> 29.6% ( 3.2) <interrupt> : eth0
> 9.3% ( 1.0) <kernel core> : __netdev_watchdog_up (dev_watchdog)
> 4.6% ( 0.5) <kernel core> : queue_delayed_work_on (delayed_work_timer_fn
> 2.8% ( 0.3) <kernel core> : irlmp_start_discovery_timer (irlmp_discovery
> _timer_expired)
>
> root@128.247.75.244:/tst# uname -a
> Linux 128.247.75.244 2.6.22.1-omap1 #3 Fri Oct 12 14:53:45 CDT 2007 armv7l GNU/L
> inux
> root@128.247.75.244:/tst# cat /proc/cpuinfo | grep OMAP
> Hardware : OMAP3430 sdp3430 board
> root@128.247.75.244:/tst#
> --------------------
Great! Time to push that patch then. I also run a quick timer tests with
select and sleep, and they're working just fine.
Tony
prev parent reply other threads:[~2007-10-12 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 20:32 [PATCH] Make dyntick work again Tony Lindgren
2007-10-12 2:05 ` Kyungmin Park
2007-10-12 14:47 ` Dirk Behme
2007-10-12 20:07 ` Tony Lindgren
2007-10-12 20:06 ` Tony Lindgren
2007-10-12 20:16 ` Woodruff, Richard
2007-10-12 20:22 ` Tony Lindgren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071012202218.GH7979@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=r-woodruff2@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox