From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm-devel <kvm@vger.kernel.org>
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Host latency peaks due to kvm-intel
Date: Thu, 23 Jul 2009 20:07:33 +0200 [thread overview]
Message-ID: <4A68A6E5.6010808@siemens.com> (raw)
Hi,
did anyone recently tried current KVM for Intel over some real-time
Linux? I'm seeing more than 500 us latency peaks on the host,
specifically during VM startup. This applies to both 2.6.29.6-rt23 and
Xenomai/I-pipe. For -rt, I both tried the included (patched) KVM modules
as well as kvm.git head with some additionally required -rt fixes.
Xenomai ran over a 2.6.30 kernel with my own KVM-enabler patch.
Early instrumentation actually points to the guest exit itself: I added
markers right before and after the assembly part of vmx_vcpu_run, and
further instrumentation reports that the next host APIC tick should go
off right inside guest mode. But KVM leaves the switching part 500 us
too late in that case - as if guest exit on external IRQs was disabled.
Will debug this further, but I'm also curious to hear other user
experiences.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next reply other threads:[~2009-07-23 18:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 18:07 Jan Kiszka [this message]
2009-07-23 19:43 ` Host latency peaks due to kvm-intel Gregory Haskins
2009-07-24 9:41 ` Jan Kiszka
2009-07-24 12:01 ` Gregory Haskins
2009-07-25 8:15 ` Avi Kivity
2009-07-25 9:55 ` Jan Kiszka
2009-07-25 13:27 ` Avi Kivity
2009-07-26 14:23 ` Jan Kiszka
2009-07-26 19:16 ` H. Peter Anvin
2009-07-27 1:11 ` Yang, Sheng
2009-07-27 9:08 ` cpuinfo and HVM features (was: Host latency peaks due to kvm-intel) Jan Kiszka
2009-07-27 9:29 ` Yang, Sheng
2009-07-27 10:31 ` cpuinfo and HVM features Avi Kivity
2009-07-25 14:52 ` Host latency peaks due to kvm-intel Avi Kivity
2009-07-26 10:34 ` Sujit Karataparambil
2009-07-26 14:34 ` Jan Kiszka
2009-07-26 14:45 ` Avi Kivity
2009-07-26 14:52 ` Jan Kiszka
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=4A68A6E5.6010808@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.