Alexander Graf wrote:
Of course, this all depends on the workload. For kernbench style
benchmarks nested NPT probably gives you a bigger win, but anything
doing IO is slowed down way more than it has to now.
What is causing 17K pio exits/sec? What port numbers?
Any hints on how to easily find that out? For someone who's too stupid
to get kvmtrace working :-).
You can always printk() every 1000 loops, but kvmtrace is actually
pretty easy to use. Compile it in, run your guest (pinning to one cpu
deconfuses the output), run kvmtrace -o blah, then use
'./kvmtrace_format formats' as a filter on the binary output.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
