From: Michael Tokarev <mjt@tls.msk.ru>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>, kvm <kvm@vger.kernel.org>
Subject: Re: kvm guest: hrtimer: interrupt too slow
Date: Sat, 10 Oct 2009 13:18:16 +0400 [thread overview]
Message-ID: <4AD05158.8030503@msgid.tls.msk.ru> (raw)
In-Reply-To: <4ACFBA6E.7030901@msgid.tls.msk.ru>
Michael Tokarev wrote:
> Frederic Weisbecker wrote:
[]
>>>> Was there swapping going on?
>>> Not as far as I can see, and sar output agrees.
>>
>> But I can read this from you guest traces:
I missed this one yesterday. Note it's GUEST traces
indeed. Higher (read: non-zero) pgp{in,out} and faults
values happens in *guest*, not on host (original question
was if we've swapping in HOST, which'd explain the timer
issues)
[cutting extra all-zero columns]
>> pgpgin/s pgpgout/s fault/s pgfree/s
>> 11:44:47 0.00 32.32 907.07 277.78
>> 11:44:48 27.59 22.99 44.83 150.57
>> 11:44:49 0.00 33.68 22.11 218.95
>> [...]
>> 21:46:54 0.00 31.68 16.83 90.10
>> 21:46:55 0.00 108.00 17.00 89.00
>> 21:46:56 9.76 482.93 3890.24 439.02
>> 21:46:57 0.00 760.00 8627.00 1133.00
>> 21:46:58 0.00 84.85 2612.12 138.38
>> 21:46:59 0.00 16.00 17.00 90.00
>>
>> So it looks like there was some swapping in when the hrtimer (spuriously)
>> hanged.
One possible guess. Since the guest hanged for some time, the
higher values there might be a result of accumulated values for
several seconds.
> It's not swapping. Swapping is in a separate table, with columns titled
> pswpin/s and pswpout/s -- first table.
>
> On my home machine with no swap at all, 4gig memory and 2gig free,
> pgpgin and pgpgout are increasing too.
>
> Also, while in the second case (21:46:56) there's actually some
> noticeable activity (page faults at least), in first case that
> activity is modest.
>
> Note there's no documentation for /proc/vmstat file :)
>
> /mjt
next prev parent reply other threads:[~2009-10-10 9:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 13:12 kvm guest: hrtimer: interrupt too slow Michael Tokarev
2009-09-29 13:47 ` Avi Kivity
2009-09-29 13:58 ` Michael Tokarev
2009-10-05 10:47 ` Avi Kivity
2009-10-03 23:12 ` Marcelo Tosatti
[not found] ` <4AC88E7E.8050909@msgid.tls.msk.ru>
2009-10-05 0:50 ` Marcelo Tosatti
2009-10-05 9:31 ` Michael Tokarev
2009-10-06 13:30 ` Michael Tokarev
2009-10-07 23:17 ` Frederic Weisbecker
2009-10-08 0:54 ` Marcelo Tosatti
2009-10-08 7:54 ` Michael Tokarev
2009-10-08 8:06 ` Thomas Gleixner
2009-10-08 8:14 ` Michael Tokarev
2009-10-08 9:29 ` Thomas Gleixner
2009-10-08 14:06 ` Michael Tokarev
2009-10-08 15:06 ` Thomas Gleixner
2009-10-08 19:52 ` Marcelo Tosatti
2009-10-09 21:22 ` Michael Tokarev
2009-10-09 22:27 ` Frederic Weisbecker
2009-10-09 22:34 ` Michael Tokarev
2009-10-10 9:18 ` Michael Tokarev [this message]
2009-10-10 9:24 ` Frederic Weisbecker
2009-10-10 17:37 ` Marcelo Tosatti
2009-10-08 8:05 ` Thomas Gleixner
2009-10-08 19:22 ` Marcelo Tosatti
2009-10-08 20:25 ` Thomas Gleixner
2009-10-08 21:02 ` Michael Tokarev
2009-10-10 17:32 ` [PATCH] tune hrtimer_interrupt hang logic Marcelo Tosatti
2009-10-08 8:09 ` kvm guest: hrtimer: interrupt too slow Michael Tokarev
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=4AD05158.8030503@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=fweisbec@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).