public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	linux-kernel
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: kvm & dyntick
Date: Fri, 12 Jan 2007 07:20:07 +0100	[thread overview]
Message-ID: <20070112062006.GA32714@elte.hu> (raw)
In-Reply-To: <45A66106.5030608-atKUWr5tajBWk0Htik3J/w@public.gmane.org>


* Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> 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.

	Ingo

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11 16:08 kvm & dyntick Avi Kivity
     [not found] ` <45A66106.5030608-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-12  5:34   ` Rik van Riel
2007-01-12  6:20   ` Ingo Molnar [this message]
     [not found]     ` <20070112062006.GA32714-X9Un+BFzKDI@public.gmane.org>
2007-01-12 10:19       ` Ingo Molnar
     [not found]         ` <20070112101931.GA11635-X9Un+BFzKDI@public.gmane.org>
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:
  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=20070112062006.GA32714@elte.hu \
    --to=mingo-x9un+bfzkdi@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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