From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Omar Khan <okhan-e94Sedi4moU@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: VM entry/exit time
Date: Tue, 01 May 2007 17:00:35 +0300 [thread overview]
Message-ID: <46374803.4040105@qumranet.com> (raw)
In-Reply-To: <loom.20070501T154537-210-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
Omar Khan wrote:
> hi,
>
> I am measuring the VM enty/exit time on the following two machines by
> recording the time it takes to make n number of vmcalls :
>
> 1. Lenovo Think Centre, Intel Pentium D, 2 Cores, 3GHz with 3G of memory
> 2. Dell Inspiron 6400 , Intel Core Duo, 2 Cores, 2 GHz with 1G of memory
>
> Surprisingly it takes almost 3 times longer on the Lenovo to make a vmcall.
> Anyone have any idea what might be causing this? Running kvm on suse10.2 on both
> the systems.
>
>
It's not surprising at all. VT is improving at a rapid pace. I suspect
that on a Core 2 you will see faster speeds, and more improvements are
promised with newer processors.
Note that recent kvm versions have improved vmexit latency independently
of the processor, and this is continuing too.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-05-01 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 13:54 VM entry/exit time Omar Khan
[not found] ` <loom.20070501T154537-210-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-05-01 14:00 ` Avi Kivity [this message]
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=46374803.4040105@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=okhan-e94Sedi4moU@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