[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1504081044130.3845@nanos>
Date: Wed, 8 Apr 2015 10:50:37 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Thavatchai Makphaibulchoke <thavatchai.makpahibulchoke@...com>
cc: Steven Rostedt <rostedt@...dmis.org>,
Thavatchai Makphaibulchoke <tmac@...com>,
linux-kernel@...r.kernel.org, mingo@...hat.com,
linux-rt-users@...r.kernel.org, umgwanakikbuti@...il.com,
Peter Zijlstra <peterz@...radead.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: [PATCH v2 1/2] rtmutex Real-Time Linux: Fixing kernel BUG at
kernel/locking/rtmutex.c:997!
On Tue, 7 Apr 2015, Thavatchai Makphaibulchoke wrote:
> On 04/06/2015 07:59 PM, Steven Rostedt wrote:
> In this case we are not actually boosting the idle_task priority, which
> should be OK. But the warning could be very overwhelming on some
> platforms. TO keep the warning, I decided not to boots priority. Please
> let me know if you have any suggestion.
Don't even try to get this working. Taking the lock in idle/interrupt
context is just plain wrong.
The proper solution is to get rid of the locking requirement and that
needs some thought on the timer wheel code.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists