From: Carsten Emde <C.Emde@osadl.org>
To: Dong Liu <dliu.cn@gmail.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: cpu stall and hyperthread
Date: Fri, 06 Jul 2012 23:01:35 +0200 [thread overview]
Message-ID: <4FF7522F.8020909@osadl.org> (raw)
In-Reply-To: <4FF70C59.40801@gmail.com>
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.
next prev parent reply other threads:[~2012-07-06 21:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FEBCDDE.60503@gmail.com>
2012-07-03 20:10 ` cpu stall and hyperthread Dong Liu
2012-07-04 1:13 ` Paul E. McKenney
2012-07-04 17:27 ` Dong Liu
2012-07-04 22:52 ` Carsten Emde
2012-07-05 18:41 ` Dong Liu
2012-07-05 22:48 ` Carsten Emde
2012-07-06 6:07 ` Dong Liu
2012-07-05 23:02 ` Carsten Emde
2012-07-06 6:04 ` Dong Liu
2012-07-05 18:48 ` Dong Liu
2012-07-06 6:20 ` Dong Liu
2012-07-06 11:40 ` Carsten Emde
2012-07-06 16:03 ` Dong Liu
2012-07-06 21:01 ` Carsten Emde [this message]
2012-07-09 4:33 ` Dong Liu
2012-07-09 6:53 ` Carsten Emde
2012-07-09 14:46 ` Dong Liu
2012-07-06 15:58 ` Dong Liu
2012-07-06 17:32 ` Dong Liu
2012-07-12 20:27 ` Dong Liu
2012-06-28 3:23 Dong Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FF7522F.8020909@osadl.org \
--to=c.emde@osadl.org \
--cc=dliu.cn@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.