Hello,

I have a problem where a vcpu is spinning over a EXIT_REASON_PAUSE_INSTRUCTION forever. This VMEXIT is caused by a spin-lock. The entire gust system blocks. As my code has not spin-locks, probably it is invoking a system call that invokes a spin-lock.
I'm interested in knowing the trace of the running process.
the problem is:

I have a vcpu stopped, then gdb and ftrace do not work.

my question is, is it possible to obtain the call trace (of a guest process running under a certain vcpu) from the structures in kvm?

Oscar
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to