From: Dong Liu <dliu.cn@gmail.com>
To: Carsten Emde <C.Emde@osadl.org>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: cpu stall and hyperthread
Date: Fri, 06 Jul 2012 02:07:12 -0400 [thread overview]
Message-ID: <4FF68090.5050605@gmail.com> (raw)
In-Reply-To: <4FF619D5.3090206@osadl.org>
Hi Carsten,
Thanks! I'll try to take a look at these systems.
Cheers!
Dong
On 7/5/12 6:48 PM, Carsten Emde wrote:
> Hi Dong,
>
>> I tried to disable CONFIG_RT_GROUP_SCHED, but I still got cpu stalls!
> Hmm, sorry. I hoped it would work.
>
>> Is there a recommended config for the RT patch?
> Not really. In the x86 distro case, we base everything on the distro
> configuration, e.g. using
> cp /boot/config-`uname -r` .config
>
> We then disable CONFIG_RT_GROUP_SCHED and CONFIG_DEBUG_STACKOVERFLOW,
> because they are known to cause trouble and long latencies,
> respectively. In addition, we enable diagnostics such a latency
> histograms. That's all.
>
> An alternative approach would be to select a QA farm system that is
> close to your hardware and distro and use the same settings on your
> system. A list of all farm systems sorted by distro is here ->
> https://www.osadl.org/?id=1070; clicking on the system name in the first
> row of this table will display its entire profile. This includes kernel
> parameter, hardware data and, of course, the kernel configuration.
> Sometimes, there is also a quilt series, in case we temporarily use
> off-tree patches that are on their way to mainline. Would be interesting
> to see whether your system also stalls when a configuration is used that
> is successful here.
>
> -Carsten.
next prev parent reply other threads:[~2012-07-06 6:07 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 [this message]
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
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=4FF68090.5050605@gmail.com \
--to=dliu.cn@gmail.com \
--cc=C.Emde@osadl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).