From: Avi Kivity <avi@qumranet.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: kvm & dyntick
Date: Thu, 11 Jan 2007 18:08:38 +0200 [thread overview]
Message-ID: <45A66106.5030608@qumranet.com> (raw)
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)
What are the current plans wrt dyntick? Is it planned for 2.6.21?
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2007-01-11 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 16:08 Avi Kivity [this message]
2007-01-12 5:34 ` kvm & dyntick Rik van Riel
2007-01-12 6:20 ` Ingo Molnar
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:
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=45A66106.5030608@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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