From: Laszlo Ersek <lersek@redhat.com>
To: Jan Beulich <JBeulich@suse.com>, Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com, Joe Jin <joe.jin@oracle.com>,
Zhenzhong Duan <zhenzhong.duan@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH] remove blocked time accounting from xen "clockchip"
Date: Thu, 20 Oct 2011 17:02:41 +0200 [thread overview]
Message-ID: <4EA03811.5090502@redhat.com> (raw)
In-Reply-To: <4EA031B0.2010400@redhat.com>
On 10/20/11 16:35, Laszlo Ersek wrote:
> I'm convinced the patch is correct, and only the commit message might
> need a small fix (mentioning cpu_idle()).
I forgot to say that I also added counters to xen_timer_interrupt(),
account_idle_ticks() (called from cpu_idle()), and the idle time branch
of account_process_tick(). (The last one is reached from
xen_timer_interrupt() via event_handler == &tick_nohz_handler, after
highres=off was passed). When the VM was left alone, they were
increasing in strict lock-step.
account_idle_time()
<- account_idle_ticks()
<- tick_nohz_restart_sched_tick()
<- cpu_idle()
<- account_process_tick()
<- update_process_times()
<- tick_nohz_handler() [highres=off]
<- xen_timer_interrupt()
<- (tick_periodic())
<- (tick_sched_timer())
The timer interrupt appears to kick cpu_idle(), and the latter accounts
for the time spent idly.
Laszlo
next prev parent reply other threads:[~2011-10-20 15:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 20:42 [PATCH] remove blocked time accounting from xen "clockchip" Laszlo Ersek
2011-10-19 7:51 ` Jan Beulich
2011-10-19 14:54 ` Laszlo Ersek
2011-10-20 14:35 ` Laszlo Ersek
2011-10-20 15:02 ` Laszlo Ersek [this message]
2011-10-26 20:52 ` Konrad Rzeszutek Wilk
2011-11-09 13:35 ` Jan Beulich
2011-11-09 17:47 ` Laszlo Ersek
2011-11-10 8:32 ` Jan Beulich
2011-11-10 18:05 ` Jeremy Fitzhardinge
2012-01-19 19:42 ` Konrad Rzeszutek Wilk
2012-01-20 9:57 ` Jan Beulich
2012-01-20 16:00 ` Konrad Rzeszutek Wilk
2012-01-23 22:07 ` Konrad Rzeszutek Wilk
2011-12-21 8:32 ` Jan Beulich
2011-12-21 13:53 ` Laszlo Ersek
2011-12-21 14:58 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2011-12-22 8:49 Jan Beulich
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=4EA03811.5090502@redhat.com \
--to=lersek@redhat.com \
--cc=JBeulich@suse.com \
--cc=jeremy@goop.org \
--cc=joe.jin@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=zhenzhong.duan@oracle.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.