From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Dan <berkovid-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: performance specs on VT-x vmenter/exit
Date: Thu, 06 Dec 2007 21:06:26 +0200 [thread overview]
Message-ID: <47584832.9010708@qumranet.com> (raw)
In-Reply-To: <4758442B.8060401-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
Anthony Liguori wrote:
>>
>>
>> Have a look at user/test/x86/vmexit.c, which does exactly that.
>>
>>
>
> That only gives you the combined count of a vmenter and vmexit.
Right; furthermore it measures kvm overhead and not just instruction
latency.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
next prev parent reply other threads:[~2007-12-06 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 18:09 performance specs on VT-x vmenter/exit Dan
[not found] ` <fe801d6f0712061009r7b6c64b5qa1ad17722036301b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-06 18:36 ` Avi Kivity
[not found] ` <47584142.10600-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-06 18:49 ` Anthony Liguori
[not found] ` <4758442B.8060401-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-12-06 19:06 ` Avi Kivity [this message]
[not found] ` <47584832.9010708-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-06 19:56 ` Anthony Liguori
[not found] ` <475853E0.7080005-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-12-06 21:17 ` Dan
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=47584832.9010708@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org \
--cc=berkovid-Re5JQEeQqe8AvxtiuMwx3w@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