On Tue, 2015-04-07 at 13:23 +0200, Thomas Gleixner wrote:
> On Mon, 6 Apr 2015, Thavatchai Makphaibulchoke wrote:
>
> > This patch fixes the problem that the ownership of a mutex acquired
> > by an interrupt handler(IH) gets incorrectly attributed to the
> > interrupted thread.
>
> An hard interrupt handler is not allowed to take a mutex. End of
> story, nothing to fix here.
Well, the patch that started this thread..
timers-do-not-raise-softirq-unconditionally.patch
..(attributed to you) was picked up in -rt (perhaps erroneously) to
get nohz_full working, and then reverted due to the deadlock detector
getting properly angry. All of this is about reinstating it.
I posted a patchlet to simply subtract softirqd from the ->nr_running
check, which gets nohz_full working in -rt sans illegal activity.
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
