Jan Kiszka wrote: > Avi Kivity wrote: >> Seeing vmx_vcpu_run() in there confuses me, as it always runs with >> interrupts disabled (it does dispatch NMIs, so we could be seeing an NMI). > > The point is that the cyclictest does not find large latencies when kvm > is not happening to start or stop right now. And if you are thinking > about NMIs triggered by the kvm code on vm-exit: I also instrumented > that code path, and it is not taken in case of the long delay.
Actually, that instrumentation was for an older version. In this one here, the vm-entry/exit block is clearly framed by traced vmcs_xxx calls. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
