All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dong Liu <dliu.cn@gmail.com>
To: linux-rt-users@vger.kernel.org
Subject: Re: cpu stall and hyperthread
Date: Fri, 06 Jul 2012 13:32:24 -0400	[thread overview]
Message-ID: <4FF72128.2070804@gmail.com> (raw)
In-Reply-To: <4FF68396.2010904@gmail.com>

I think I narrowed down this problem a little bit.

When I set RCU_BOOST, it was quite easy to generate cpu stall, but the 
system is not really hung. So I turned off the cpu stall checking by doing

echo "1" > /sys/module/rcutree/parameters/rcu_cpu_stall_suppress

at boot time.

Then I tried to start VMs. Sometime VM started fine, sometime VM hung, I 
need to destroied. When the starting of VM hung, the WCHAN of qemu-kvm 
was wait_rcu_gp. And when I did "virsh destroy id", the VM also hung, 
qemu-kvm was stuck at rcu_barrier. It really has something to do with KVM.

Dong

On 7/6/12 2:20 AM, Dong Liu wrote:
> I can quite reliably trigger this cpu stall error now. Just try to start
> several KVM guests.
>
> It seems the kvm progress uses too much CPU?
>
> Since ps -efl showed that the priority of the kvm kernel thread was -20.
> So I tried,
>
> CONFIG_RCU_BOOST=y
> CONFIG_RCU_BOOST_PRIO=50
> CONFIG_RCU_BOOST_DELAY=500
>
> But I still got the same error :(
>
> Are there any way I can use to narrow down this error?
>
> Is it possible to non-preemptible RCU in PREEMPT_RT kernel? I know it
> will reduce the system's RT performance, but we can make sure the reason
> of this cpu stall error is the preemptible RCU
>
> Thanks,
>
> Dong
>
> On 6/27/12 11:22 PM, Dong Liu wrote:
>> Hi,
>>
>> I'm running 3.4.3-rt11 and 3.2.18-rt29 on a system with Intel I7 860, I
>> noticed that with hyperthread enabled, I'm getting kernel error
>>
>> rcu_preempt detected stalls on CPUs/tasks: { 3} (detected by 5, t=60002
>> jiffies)
>>
>> But with hyperthread disabled, no such error.
>>
>> Is preempt_rt not supposed to be used with hyperthread?
>>
>> Thanks,
>>
>> Dong
>>
>> P.S.
>


  parent reply	other threads:[~2012-07-06 17:32 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
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 [this message]
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=4FF72128.2070804@gmail.com \
    --to=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.