Date: Wed, 22 Mar 2017 11:01:16 -0700
From: Steven Rostedt <rostedt@goodmis.org>
To: Julia Cartwright <julia@ni.com>
Cc: Lionel Debieve <lionel.debieve@st.com>,
        <linux-rt-users@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <bigeasy@linutronix.de>, <tglx@linutronix.de>
Subject: Re: [PATCH RT 1/1] remoteproc: Prevent schedule while atomic
Message-ID: <20170322110116.4b14dafd@vmware.local.home>
In-Reply-To: <20170322173759.GK10423@jcartwri.amer.corp.natinst.com>
References: <1490195923-9560-1-git-send-email-lionel.debieve@st.com>
        <20170322173759.GK10423@jcartwri.amer.corp.natinst.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 690
Lines: 24

On Wed, 22 Mar 2017 12:37:59 -0500
Julia Cartwright <julia@ni.com> wrote:

> Which kernel were you testing on, here?  From what I can tell, this
> should have been fixed with Thomas's commit:
> 
>    2a1d3ab8986d ("genirq: Handle force threading of irqs with primary
> and thread handler")

Thanks Julia for looking into this. I just looked at the code, and saw
that it does very little with the lock held, and was fine with the
conversion. But if that interrupt handler should be in a thread, we
should see if that's the issue first.

> 
> Which landed in 4.4.  It forces the primary handler to be threaded as
> well.
> 

Lionel,

Can you check if this is an issue with 4.4 too?

-- Steve