Hi Dong,
I can quite reliably trigger this cpu stall error now. Just try to start
several KVM guests.
Good. BTW, we do repeated long-term tests 14 times per day with a single
kvm guest that runs on two cores and conducts a number of CPU
benchmarks. (https://www.osadl.org/?id=931) - never had this problem. So
it may be related to running more than a single kvm guest.
I don't have /sys/kernel/debug/tracing/ directory. The kernel doc says
turn on CONFIG_KPROBE_TRACING. But I could not find this config.
Either tracing is not configured or the debugfs is not mounted or it is
mounted elsewhere.
Try
mount -t debugfs nodev /sys/kernel/debug
and, if the tracer still is not there, do
make menuconfig
Kernel hacking --->
[*] Tracers --->
[*] Kernel Function Tracer
[*] enable/disable ftrace tracepoints dynamically
and recompile the kernel.
If you want the debugfs to be mounted at boot time, append
nodev /sys/kernel/debug debugfs defaults 0 0
to /etc/fstab.
-Carsten.
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
