public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anders <mail@flac.kalibalik.dk>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm@vger.kernel.org
Subject: Re: KVM power usage - high wakeup rates
Date: Mon, 23 Jun 2008 19:10:17 +0200	[thread overview]
Message-ID: <485FD8F9.9020100@flac.kalibalik.dk> (raw)
In-Reply-To: <485F0F99.6060103@qumranet.com>

Avi Kivity wrote:
> Anders wrote:
>> 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.

The -no-kvm-pit did change things. However, there is still a periodic tick:

Top causes for wakeups:
  34,7% (102,0)   qemu-system-x86 : sys_timer_settime (posix_timer_fn)
  34,0% (100,0)   qemu-system-x86 : __kvm_migrate_timers (apic_timer_fn)
  13,8% ( 40,7)      <kernel IPI> : function call interrupts

For comparison, this is my normal output. This is with the same kernel 
modules, but the userspace from Ubuntu 8.04:

Top causes for wakeups:
  50,2% ( 66,0)      <kernel IPI> : function call interrupts
  11,3% ( 14,9)               kvm : apic_mmio_write (apic_timer_fn)

>> In general, what are the best host/guest settings for a low number of 
>> wakeups?
>
> dyntick on both.
>

Sure. I guess my question was how to achieve that. Things like the 
-no-kvm-pit advice. Also, I have used "clocksource=tsc acpi=force" on 
the guest to get it to dyntick. But that seems to no longer work. So I 
was wondering whether there was some known configuration that was 
supposed to work.


Anders.


      reply	other threads:[~2008-06-23 17:10 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
2008-06-23 17:10       ` Anders [this message]

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=485FD8F9.9020100@flac.kalibalik.dk \
    --to=mail@flac.kalibalik.dk \
    --cc=avi@qumranet.com \
    --cc=kvm@vger.kernel.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