Thanks for the lightning-fast response, guys.
I'll play around with vmexit.c and let some of this sink in.
I was hoping to get a clean count of ticks/vm[enter/exit] without the kvm
latency, and I thought putting in into the code in the kvm code in the
kernel source would accomplish something like that.
Getting counts per exit reason would be really neat too.
Thanks again, I'm sure I'll come back with more precise questions later :D
:dan
On Dec 6, 2007 2:56 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> Avi Kivity wrote:
> > 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.
>
> True. Also, I don't know what Dan is looking to measure, but the cost
> of vmexits will varying depending on the reason for exit. vmexit.c uses
> cpuid() which I suspect is slower than vmexit or pio but faster than
> pf. It would be interesting to measure the individual exit reasons.
>
> Regards,
>
> Anthony Liguori
>
>
>
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
