From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-arch@vger.kernel.org
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Paul Mackerras <paulus@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Tony Luck <tony.luck@intel.com>,
Jeremy Fitzhardinge <jeremy@xensource.com>,
Chris Wright <chrisw@sous-sol.org>,
Michael Neuling <mikey@neuling.org>
Subject: Re: [patch 0/4] [RFC] true vs. system idle cputime
Date: Wed, 15 Oct 2008 16:01:56 +0200 [thread overview]
Message-ID: <1224079316.16990.28.camel@localhost> (raw)
In-Reply-To: <20081008161958.767142939@de.ibm.com>
On Wed, 2008-10-08 at 18:19 +0200, Martin Schwidefsky wrote:
> Greetings,
> while working on the analysis of a mismatch between the cputime accounting
> numbers of z/VM as the host and Linux as the guest I started to wonder
> about the accounting of idle time. z/VM showed more cpu time for the guest
> as the guest itself. With the current code everything that the idle process
> does is accounted as idle time. If idle is sleeping that is fine, but if
> idle is actually using cpu cycles this is wrong.
>
> The question is how wrong? To find out I've implemented really precise
> accounting of true idle vs. system idle cputime for s390. A really simple
> test that wakes up 100 times per second to do some minimal work before
> going back to sleep showed 0.35% of system idle time. If you are dealing
> with lots of virtual penguins this quickly becomes significant.
>
> There are four patches in this series:
> Patch #1: Cleanup scaled / unscaled cputime accounting
> Patch #2: Change the accounting interface to allow the architectures to do
> precise idle time accounting
> Patch #3: s390 patch to improve the precision of the idle_time_us value
> Patch #4: s390 patch to implement improved idle time accounting
>
> There is one change in patch #2 that might require a change on powerpc
> and/or ia64. The generic TICK_ONESHOT/NO_HZ code calculates the number
> of ticks spent with a disabled HZ timer and accounts this as idle time.
> For a configuration for VIRT_CPU_ACCOUNTING=y this is horribly wrong.
> Either you have precise accounting or you don't. Patch #2 just removes
> the calculation for VIRT_CPU_ACCOUNTING=y. The architectures which support
> precise accounting have to deal with it on their own. This is where the
> powerpc and ia64 maintainer come into play. Would you look at patch #2
> please ?
>
> To make it clearer what happens in tick_nohz_restart_sched_tick I've added
> a new function account_idle_ticks(). And for good measure another one named
> account_steal_ticks() for xen where "interesting" things have been done
> with the account_steal_time interface.
Any news about powerpc? Do these patches break anything or does it work?
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2008-10-15 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 16:19 [patch 0/4] [RFC] true vs. system idle cputime Martin Schwidefsky
2008-10-08 16:19 ` [patch 1/4] fix scaled & unscaled cputime accounting Martin Schwidefsky
2008-10-16 4:31 ` Paul Mackerras
2008-10-08 16:20 ` [patch 2/4] idle " Martin Schwidefsky
2008-10-16 4:59 ` Paul Mackerras
2008-10-16 6:42 ` Martin Schwidefsky
2008-10-16 9:08 ` Martin Schwidefsky
2008-10-08 16:20 ` [patch 3/4] improve precision of idle accounting Martin Schwidefsky
2008-10-08 16:20 ` [patch 4/4] improve idle cputime accounting Martin Schwidefsky
2008-10-08 21:22 ` [patch 0/4] [RFC] true vs. system idle cputime Luck, Tony
2008-10-09 8:03 ` Martin Schwidefsky
2008-10-15 14:01 ` Martin Schwidefsky [this message]
2008-10-15 20:56 ` Benjamin Herrenschmidt
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=1224079316.16990.28.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=chrisw@sous-sol.org \
--cc=heiko.carstens@de.ibm.com \
--cc=jeremy@xensource.com \
--cc=linux-arch@vger.kernel.org \
--cc=mikey@neuling.org \
--cc=paulus@samba.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.