LKML Archive on
help / color / mirror / Atom feed
From: Ingo Molnar <>
To: Avi Kivity <>
Cc: kvm-devel <>,
	linux-kernel <>,
	Thomas Gleixner <>
Subject: Re: kvm & dyntick
Date: Fri, 12 Jan 2007 07:20:07 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

* Avi Kivity <> wrote:

> It occurs to me that kvm could benefit greatly from dyntick:
> dyntick-enabled host:
> - generate virtual interrupts at whatever HZ the guest programs its 
> timers, be it 100, 250, 1000 or whatever
> - avoid expensive vmexits due to useless timer interrupts
> dyntick-enabled guest:
> - reduce the load on the host when the guest is idling
>   (currently an idle guest consumes a few percent cpu)

yeah. KVM under -rt already works with dynticks enabled on both the host 
and the guest. (but it's more optimal to use a dedicated hypercall to 
set the next guest-interrupt)

> What are the current plans wrt dyntick?  Is it planned for 2.6.21?

yeah, we hope to have it in v2.6.21.

note that s390 (and more recently Xen too) uses a next_timer_interrupt() 
based method to stop the guest tick - which works in terms of reducing 
guest load, but it doesnt stop the host-side interrupt. The highest 
quality approach is to have dynticks on both the host and the guest, and 
this also gives high-resolution timers and a modernized 
time/timer-events subsystem for both the host and the guest.


  parent reply	other threads:[~2007-01-12  6:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11 16:08 Avi Kivity
2007-01-12  5:34 ` Rik van Riel
2007-01-12  6:20 ` Ingo Molnar [this message]
2007-01-12 10:19   ` Ingo Molnar
2007-01-12 17:04     ` Avi Kivity
2007-01-14  8:39       ` Ingo Molnar
2007-01-12 23:25     ` [kvm-devel] " Dor Laor
2007-01-12 23:39       ` Thomas Gleixner
2007-01-14  8:51       ` Ingo Molnar

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: kvm & dyntick' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).