From: Avi Kivity <avi@qumranet.com>
To: Anders <mail@flac.kalibalik.dk>
Cc: kvm@vger.kernel.org
Subject: Re: KVM power usage - high wakeup rates
Date: Mon, 23 Jun 2008 05:51:05 +0300 [thread overview]
Message-ID: <485F0F99.6060103@qumranet.com> (raw)
In-Reply-To: <485E59C3.1020607@flac.kalibalik.dk>
Anders wrote:
> Anthony Liguori wrote:
>> With the default options, my idle winxp guest causes about 550
>> wakeups/sec which is pretty close to what I'd expect. I don't think
>> you'll get much better than that without using a dynticks guest.
>
> According to powertop, I had about 15 kvm wakeups/sec with my previous
> setup (nohz, no display). Now I upgraded to kvm-70 and the timer
> interrupt has reappeared so I have this:
>
> Top causes for wakeups:
> 25,4% (112,4) <kernel IPI> : function call interrupts
> 22,6% (100,0) qemu-system-x86 : kvm_arch_vcpu_ioctl_run (pit_timer_fn)
> 22,6% (100,0) qemu-system-x86 : __kvm_migrate_timers (apic_timer_fn)
> 8,7% ( 38,5) qemu-system-x86 : sys_timer_settime (posix_timer_fn)
>
> What could be the cause for this change? The previous kvm was from
> Ubuntu 8.04, there are no changes in the guest.
>
Likely, the in-kernel pit. Try -no-kvm-pit.
> In general, what are the best host/guest settings for a low number of
> wakeups?
dyntick on both.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2008-06-23 2:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 5:29 KVM power usage - high wakeup rates Haydn Solomon
2008-06-19 18:26 ` Marcelo Tosatti
2008-06-19 18:58 ` Haydn Solomon
2008-06-19 18:34 ` Anthony Liguori
2008-06-19 18:59 ` Haydn Solomon
2008-06-19 20:17 ` Anthony Liguori
2008-06-22 6:53 ` Avi Kivity
2008-06-22 13:55 ` Anders
2008-06-23 2:51 ` Avi Kivity [this message]
2008-06-23 17:10 ` Anders
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=485F0F99.6060103@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=mail@flac.kalibalik.dk \
/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.