From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH] Make dyntick work again Date: Fri, 12 Oct 2007 13:22:18 -0700 Message-ID: <20071012202218.GH7979@atomide.com> References: <20071012200612.GE7979@atomide.com> <3B6D69C3A9EBCA4BA5DA60D9130274290231FFA1@dlee13.ent.ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D9130274290231FFA1@dlee13.ent.ti.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces@linux.omap.com Errors-To: linux-omap-open-source-bounces@linux.omap.com To: "Woodruff, Richard" Cc: linux-omap-open-source@linux.omap.com List-Id: linux-omap@vger.kernel.org * Woodruff, Richard [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) : 32KHz timer > 29.6% ( 3.2) : eth0 > 9.3% ( 1.0) : __netdev_watchdog_up (dev_watchdog) > 4.6% ( 0.5) : queue_delayed_work_on (delayed_work_timer_fn > 2.8% ( 0.3) : 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