On 01/17/2012 06:53 AM, David Ahern wrote: > > > On 01/16/2012 02:30 AM, Xiao Guangrong wrote: >> This tool is very like xenoprof(if i remember correctly), and traces kvm events >> smartly. currently, it supports vmexit/mmio/ioport events. >> >> Usage: >> - to trace kvm events: >> # ./perf kvm-events record >> >> - show the result >> # ./perf kvm-events report >> >> Some output are as follow: >> # ./perf kvm-events report >> Warning: Error: expected type 5 but read 4 >> Warning: Error: expected type 5 but read 0 >> Warning: unknown op '}' > > Integrating the trace-cmd plugins into perf will remedy the above errors: > https://lkml.org/lkml/2011/8/16/352 > Yes, it is great! > Unfortunately, that effort is stalled at the moment. > >> >> >> Analyze events for all VCPUs: >> >> VM-EXIT Samples Samples% Time% Avg time >> >> APIC_ACCESS 438107 44.89% 6.20% 17.91us >> EXTERNAL_INTERRUPT 219226 22.46% 8.01% 46.20us >> IO_INSTRUCTION 122651 12.57% 1.88% 19.44us >> EPT_VIOLATION 83110 8.52% 1.36% 20.75us >> PENDING_INTERRUPT 37055 3.80% 0.16% 5.38us >> CPUID 32718 3.35% 0.08% 3.15us >> EXCEPTION_NMI 23601 2.42% 0.17% 8.87us >> HLT 15424 1.58% 82.12% 6735.06us >> CR_ACCESS 4089 0.42% 0.02% 6.08us >> >> Total Samples:975981, Total events handled time:126502464.88us. > > Have you thought about dumping a time history -- something similar to > what perf-script can do with dumping events but adding in kvm-specific > analysis like what you are doing in these examples? > I will look into it and put it to my todo list if it is possible. Thanks, David! -- 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
