[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150306121921.GA10155@linutronix.de>
Date: Fri, 6 Mar 2015 13:19:21 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Thavatchai Makphaibulchoke <thavatchai.makpahibulchoke@...com>,
Thavatchai Makphaibulchoke <tmac@...com>,
linux-kernel@...r.kernel.org, mingo@...hat.com, tglx@...utronix.de,
linux-rt-users@...r.kernel.org
Subject: Re: [PATCH 3.14.25-rt22 1/2] rtmutex Real-Time Linux: Fixing kernel
BUG at kernel/locking/rtmutex.c:997!
* Steven Rostedt | 2015-02-26 09:06:10 [-0500]:
>If we can pull that off and remove all rtmutex trylocks from hardirq
>context, I would much rather do that.
>
>This hocus pocus coding is just going to lead us down the path of the
>black arts. I already have a black cat, so I'm good to go.
Okay. So what is the fix for v3.14 and other trees where the rtmutex
reworked has been integrated? Revert the optimization like I did in
v3.18?
Sebastian
--
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