From: "Yang, Sheng" <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [PATCH 0/2]KVM: In-kernel PIT model
Date: Mon, 28 Jan 2008 14:43:56 +0800 [thread overview]
Message-ID: <200801281443.56184.sheng.yang@intel.com> (raw)
Hi,
Here is the updated in-kernel PIT model. The main improvements are:
1. The support of SMP PAE host is OK now.
2. The strategy of inject timer interrupt changed. To prevent much more
interrupt injection in some SMP guest(for example, more than 50k trying for
1k interrupts per second), the strategy was changed to try to ensure last
interrupt was injected, then inject the next one. Also add time out to in
case of interrupts lost.
3. Find a bug of QEMU PIT causing a little more PIT interrupts were
injected(36.4 interrupts were injected per second, causing 2.6.16 guest timer
run faster more than 1/10). Disable QEMU PIT now.
The test result is pretty well with both UP and SMP guest, mostly with default
kernel paramters. But RHEL5/5.1 SMP
PAE guest need "clocksource=pit" to make it stable, otherwise may meet the
same problem in currently RHEL5.1 SMP PAE guest. If hang occurs, seems only
the time out part of PIT interrupts would be injected. For seems it's due to
other clocksource, I would check that later.
--
Thanks
Yang, Sheng
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next reply other threads:[~2008-01-28 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 6:43 Yang, Sheng [this message]
[not found] ` <200801281443.56184.sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2008-01-28 12:01 ` [PATCH 0/2]KVM: In-kernel PIT model Avi Kivity
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=200801281443.56184.sheng.yang@intel.com \
--to=sheng.yang-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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