public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Lukas Hejtmanek <xhejtman@ics.muni.cz>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Marcin Slusarz <marcin.slusarz@gmail.com>,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	corsac@debian.org
Subject: Re: Bootup time regression from 2.6.27 to 2.6.28-rc3+
Date: Sun, 9 Nov 2008 23:53:28 +0100	[thread overview]
Message-ID: <200811092353.30297.elendil@planet.nl> (raw)
In-Reply-To: <alpine.LFD.2.00.0811092226050.12263@localhost.localdomain>

On Sunday 09 November 2008, Thomas Gleixner wrote:
> Find below the lineup of the timers-fixes-for-linus branch of the tip
> tree (the same as Arjan posted minus the irq fixes)

I've tested with Thomas' patch set on top of v2.6.28-rc3-261-g8b805ef.

The notebook boots normally, but spends way too much time in C0.

Cheers,
FJP


POWERTOP BEFORE
===============
This is somewhere around -rc3-200 with peek_ahead disabled with a return
in the function. System is on battery after having been suspended to RAM
a few times

Note the double C0 and missing P-states.

Cn                Avg residency       P-states (frequencies)
C0 (cpu running)        ( 3.2%)
C0                0.0ms ( 0.0%)
C1                0.0ms ( 0.0%)
C2                0.9ms ( 0.1%)
C4                3.4ms (96.7%)

Wakeups-from-idle per second : 289.1    interval: 10.0s
Power usage (ACPI estimate): 9.8W (4.5 hours)

Top causes for wakeups:
  42.8% (136.5)       <interrupt> : extra timer interrupt
  30.5% ( 97.2)       <interrupt> : PS/2 keyboard/mouse/touchpad
  12.4% ( 39.5)      <kernel IPI> : Rescheduling interrupts
   3.6% ( 11.6)       <interrupt> : iwlagn
   2.5% (  8.0)   <kernel module> : mod_timer (rh_timer_func)
   1.7% (  5.4)             artsd : schedule_hrtimeout_range (hrtimer_wakeup)
   1.1% (  3.6)     <kernel core> : hrtimer_start (tick_sched_timer)
   1.0% (  3.1)       <interrupt> : acpi
   0.6% (  2.0)            kicker : schedule_hrtimeout_range (hrtimer_wakeup)
   0.4% (  1.2)           klipper : schedule_hrtimeout_range (hrtimer_wakeup)
   0.3% (  1.1)          kdesktop : schedule_hrtimeout_range (hrtimer_wakeup)
   0.3% (  1.0)      kwifimanager : schedule_hrtimeout_range (hrtimer_wakeup)
   0.3% (  1.0)     <kernel core> : enqueue_task_rt (sched_rt_period_timer)
   0.3% (  1.0)             artsd : hrtimer_start (it_real_fn)
   0.3% (  1.0)          kwrapper : do_nanosleep (hrtimer_wakeup)
   0.3% (  1.0)              kwin : schedule_hrtimeout_range (hrtimer_wakeup)
   0.3% (  0.9)              Xorg : schedule_hrtimeout_range (hrtimer_wakeup)
   0.2% (  0.5)            iwlagn : mod_timer (ieee80211_sta_timer)
   0.2% (  0.5)         gpg-agent : schedule_hrtimeout_range (hrtimer_wakeup)
   0.2% (  0.5)   hald-addon-stor : schedule_hrtimeout_range (hrtimer_wakeup)


POWERTOP AFTER
==============
Again on battery; P-states are back and the second C0 is now "polling"
(both same as with 2.6.27.4).

System permanently remains very high in C0!
Wakeups go down to ~30 without user input (keyboard/mouse activity), which
is a bit lower than I get with .27.4.

Cn                Avg residency       P-states (frequencies)
C0 (cpu running)        (49.7%)         1333 Mhz     0.0%
polling           0.0ms ( 0.0%)         1200 Mhz     0.0%
C1                0.0ms ( 0.0%)         1067 Mhz     0.0%
C2                7.5ms ( 1.9%)          800 Mhz   100.0%
C4                8.5ms (48.4%)

Wakeups-from-idle per second : 59.6     interval: 15.0s
Power usage (ACPI estimate): 9.7W (4.4 hours)

Top causes for wakeups:
  34.6% ( 36.3)       <interrupt> : PS/2 keyboard/mouse/touchpad
  16.0% ( 16.7)      <kernel IPI> : Rescheduling interrupts
   8.9% (  9.3)       <interrupt> : iwlagn
   8.4% (  8.8)       <interrupt> : extra timer interrupt
   7.8% (  8.1)   <kernel module> : mod_timer (rh_timer_func)
   5.6% (  5.9)     <kernel core> : hrtimer_start (tick_sched_timer)
   5.2% (  5.4)             artsd : schedule_hrtimeout_range (hrtimer_wakeup)
   2.9% (  3.0)            kicker : schedule_hrtimeout_range (hrtimer_wakeup)
   1.1% (  1.2)          kdesktop : schedule_hrtimeout_range (hrtimer_wakeup)
   1.0% (  1.1)              Xorg : schedule_hrtimeout_range (hrtimer_wakeup)
   1.0% (  1.0)      kwifimanager : schedule_hrtimeout_range (hrtimer_wakeup)
   1.0% (  1.0)             artsd : hrtimer_start (it_real_fn)
   1.0% (  1.0)          kwrapper : do_nanosleep (hrtimer_wakeup)
   1.0% (  1.0)              kwin : schedule_hrtimeout_range (hrtimer_wakeup)
   1.0% (  1.0)           klipper : schedule_hrtimeout_range (hrtimer_wakeup)
   0.5% (  0.5)   hald-addon-stor : schedule_hrtimeout_range (hrtimer_wakeup)
   0.5% (  0.5)            iwlagn : mod_timer (ieee80211_sta_timer)
   0.5% (  0.5)     <kernel core> : __mod_timer (neigh_periodic_timer)
   0.4% (  0.5)         gpg-agent : schedule_hrtimeout_range (hrtimer_wakeup)
   0.4% (  0.4)           knotify : schedule_hrtimeout_range (hrtimer_wakeup)

In both cases there's no C3, but I think that's because C3 changes to C4
when on battery?

Cheers,
FJP

  parent reply	other threads:[~2008-11-09 22:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 17:33 Bootup time regression from 2.6.27 to 2.6.28-rc3+ Lukas Hejtmanek
2008-11-09  0:06 ` Rafael J. Wysocki
2008-11-09  4:55   ` Arjan van de Ven
2008-11-09  8:56     ` Lukas Hejtmanek
2008-11-09 10:52       ` Marcin Slusarz
2008-11-09 11:33         ` Lukas Hejtmanek
2008-11-09 13:24           ` Rafael J. Wysocki
2008-11-09 20:09             ` Lukas Hejtmanek
2008-11-09 20:28               ` Arjan van de Ven
2008-11-09 20:34                 ` Lukas Hejtmanek
2008-11-09 21:24                   ` Arjan van de Ven
2008-11-09 21:38                     ` Lukas Hejtmanek
2008-11-09 21:43                     ` Lukas Hejtmanek
2008-11-09 21:57                       ` Thomas Gleixner
2008-11-10  8:12                         ` Lukas Hejtmanek
2008-11-10 12:16                         ` Lukas Hejtmanek
2008-11-09 21:56                     ` Thomas Gleixner
2008-11-09 22:46                       ` Bernhard Schmidt
2008-11-09 22:53                       ` Frans Pop [this message]
2008-11-14  1:45                       ` Frans Pop
2008-11-15 17:16                         ` Frans Pop
2008-11-15 18:04                           ` Arjan van de Ven
2008-11-16 19:27                         ` [2.6.28-rc5] TSC sync error and high hrtimer_start (was: Bootup time regression from 2.6.27 to 2.6.28-rc3+) Frans Pop
2008-11-17  2:18                           ` Frans Pop
2008-11-10 13:45                     ` Bootup time regression from 2.6.27 to 2.6.28-rc3+ Yves-Alexis Perez
2008-11-11 17:33                       ` Len Brown
2008-11-09 20:39                 ` Linus Torvalds
2008-11-09 20:48                   ` Arjan van de Ven
2008-11-09 14:20       ` Frans Pop
2008-11-09 15:14         ` Lukas Hejtmanek

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=200811092353.30297.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=arjan@infradead.org \
    --cc=corsac@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=xhejtman@ics.muni.cz \
    /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