From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, power@bughost.org
Subject: Re: What is "extra timer interrupt" in powertop output?
Date: Tue, 26 Aug 2008 10:23:43 +0100 [thread overview]
Message-ID: <48B3CB9F.4070903@tuffmail.co.uk> (raw)
Andrey Borzenkov wrote:
> After disabling CD-ROM polling the next top-100 winner is "extra timer
> interrupt":
>
> Cn Avg residency P-states (frequencies)
> C0 (cpu running) ( 4.2%) 750 Mhz 0.0%
> polling 0.0ms ( 0.0%) 500 Mhz 100.0%
> C1 0.0ms ( 0.0%)
> C2 0.9ms (95.8%)
>
>
> Wakeups-from-idle per second : 1101.2 interval: 5.0s
> Power usage (ACPI estimate): 11.7W (2.2 hours)
>
> Top causes for wakeups:
> 31.6% ( 8.4) : extra timer interrupt
> 15.0% ( 4.0) hald-addon-acpi : schedule_timeout (process_timeout)
>
> I assume, this is what is simply called "timer":
> {pts/1}:~%> cat /proc/interrupts
> CPU0
> 0: 9060975 XT-PIC-XT timer
>
> Any way to find out why there are so many of them? System is using dynamic
> ticks:
> {pts/1}:~/src/linux-git%> grep NO_HZ /boot/config
> CONFIG_NO_HZ=y
>
One possible reason is the hardware timer used cannot delay for long
periods, so the kernel has to wake up more often than necessary. Um.
This doesn't seem to be explained well in docs.
The question is do you have HPET (good hardware timer) enabled?
Enabling HPET is supposed to be one of the things powertop suggests.
Sometimes it is a BIOS option, or may require a kernel option, or may
not be supported on your motherboard.
Alan
next reply other threads:[~2008-08-26 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 9:23 Alan Jenkins [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-24 10:26 What is "extra timer interrupt" in powertop output? Andrey Borzenkov
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=48B3CB9F.4070903@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=power@bughost.org \
/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