From: Sadasivan Shaiju <sshaiju@mvista.com>
To: linux-rt-users@vger.kernel.org
Cc: shaiju_sada@yahoo.com
Subject: PATCH[2.6.32] scheduler patch
Date: Mon, 11 Aug 2014 14:27:56 -0700 [thread overview]
Message-ID: <6d91e5247004ea6dea84c08dfc12b508@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Hi,
I work for Montavista (Cavium Inc) as a Technical Lead . I want to
push some of the kernel patches to rt community (2.6.32 kernel 2.6.33
rt patch) , so that It will go to the main line These patches are
reviewed and approved by our system Architect. I request you to
include in the main line . These issues were reported by our
customer CISCO.
Problem Description:
In some cases the task state of a task is set incorrectly, resulting in
a
hung task.
Root Cause:
Trying to claim the BKL while PREEMPT_ACTIVE is set will result in
__schedule returning immediately in __mutex_lock_common(). This means
the task state will not be set to running by the wakeup, and it also
means
that the kernel will just sit there and spin waiting for the mutex,
which
is bad.
This occurs in __cond_resched, which calls schedule() with
PREEMPT_ACTIVE
set. The other places that call schedule() with PREEMPT_ACTIVE set have
special code that plays with the BKL.
How Solved:
To fix this, moved releasing and reclaiming the BKL to outside setting
the PREEMPT_ACTIVE bit.
I request you to include the above patch to the main line . If any
questions please contact me at sshaiju@mvista.com
(shaiju_sada@yahoo.com)
Regards,
Shaiju.
[-- Attachment #2: 5913-Fix-BKL-problems-leading-to-bad-task-state.docx --]
[-- Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document, Size: 17031 bytes --]
next reply other threads:[~2014-08-11 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 21:27 Sadasivan Shaiju [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-12 0:36 PATCH[2.6.32] scheduler patch Sadasivan Shaiju
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=6d91e5247004ea6dea84c08dfc12b508@mail.gmail.com \
--to=sshaiju@mvista.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=shaiju_sada@yahoo.com \
/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).