All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qiang Huang <h.huangqiang@huawei.com>
To: Li Zefan <lizefan@huawei.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	zhangwei <jovi.zhangwei@huawei.com>
Subject: Re: cgroup_fj tests will stick the nort kernel
Date: Thu, 25 Apr 2013 16:56:52 +0800	[thread overview]
Message-ID: <5178EFD4.9060806@huawei.com> (raw)
In-Reply-To: <5178ECEE.4070907@huawei.com>

On 2013/4/25 16:44, Li Zefan wrote:
>> And the patch below, I added your signed-off-by if it looks good to you.
> 
> Don't...
> 
>> Here is the patch seems solve the problem, it looks all good in my box, my
>> only concern is how will this affect our RT code.
>>
>>
>> >From 8e4fa4e9a7b510bdaf90b8140ce1e847375abccf Mon Sep 17 00:00:00 2001
>> From: Qiang Huang <h.huangqiang@huawei.com>
>> Date: Thu, 25 Apr 2013 10:22:01 +0800
>> Subject: [PATCH] sched: don't clear PF_THREAD_BOUND in select_fallback_rq
>>
>> This is revert of "sched-clear-pf-thread-bound-on-fallback-rq.patch"
>> (commit 0d939066acdcb in v3.4-rt),.
>>
>> Select_fallback_rq() can be easilly called during system boot, because
>> select_task_rq_fair() just return task_cpu(p) for bounded kernel threads,
>> which is 0 during system boot and not in tsk_cpus_allowed, so
>> select_fallback_rq() is called and PF_THREAD_BOUND is cleared. In my
>> box, 1/3 bounded kernel threads will clear that flag after boot.
>>
>> And it will cause problems, for example:
>> # for pid in `ps -e -o pid`; do taskset -p -c 0-15 $pid; done
>> this command will cause system hung.
>>
>> What's more, I don't see why we need to clear this flag any more,
>> because "cpu/rt: Rework cpu down for PREEMPT_RT" already remove the
>> optimization for PF_THREAD_BOUND on migrate_disable/enable.
>>
>> Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
>> Signed-off-by: Li Zefan <lizefan@huawei.com>
> 
> You shoudn't have added my SOB... I didn't write this patch and I didn't
> even sugguest this fix or check if this is a correct fix.
> 
> Please read Documentation/SubmittingPatches to learn how SOB should
> be used.
> 

OK, I'll resend it.



  reply	other threads:[~2013-04-25  8:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19  7:30 cgroup_fj tests will stick the nort kernel Qiang Huang
2013-04-20  2:00 ` Qiang Huang
2013-04-20  7:21   ` Li Zefan
2013-04-22  9:39 ` Li Zefan
2013-04-22 16:00   ` Steven Rostedt
2013-04-23  5:51     ` Li Zefan
2013-04-23 10:46       ` Li Zefan
2013-04-25  6:11       ` Qiang Huang
2013-04-25  8:44         ` Li Zefan
2013-04-25  8:56           ` Qiang Huang [this message]
2013-04-25 12:53         ` Steven Rostedt
2013-04-30 14:21     ` Luis Claudio R. Goncalves

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=5178EFD4.9060806@huawei.com \
    --to=h.huangqiang@huawei.com \
    --cc=jovi.zhangwei@huawei.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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.