Hi,
Looking at the thread discussion, except architecture discussion around the
IRQF_ONESHOT, I think it could go to upstream too.
I'll re-upload patch for upstream.
Thanks for reviewing.
BR,
Lionel
On 03/30/2017 09:54 AM, Lee Jones wrote:
> On Wed, 29 Mar 2017, Sebastian Andrzej Siewior
Hi,
Looking at the thread discussion, except architecture discussion around the
IRQF_ONESHOT, I think it could go to upstream too.
I'll re-upload patch for upstream.
Thanks for reviewing.
BR,
Lionel
On 03/30/2017 09:54 AM, Lee Jones wrote:
> On Wed, 29 Mar 2017, Sebastian Andrzej Siewior
On Wed, 29 Mar 2017, Sebastian Andrzej Siewior wrote:
> On 2017-03-22 09:05:58 [-0700], Steven Rostedt wrote:
> > On Wed, 22 Mar 2017 16:18:43 +0100
> > Lionel Debieve wrote:
> >
> > > Use raw_spin_lock in enable/disable channel as it comes from
> > > interrupt context.
>
On Wed, 29 Mar 2017, Sebastian Andrzej Siewior wrote:
> On 2017-03-22 09:05:58 [-0700], Steven Rostedt wrote:
> > On Wed, 22 Mar 2017 16:18:43 +0100
> > Lionel Debieve wrote:
> >
> > > Use raw_spin_lock in enable/disable channel as it comes from
> > > interrupt context.
> > >
> > > BUG:
On 2017-03-22 09:05:58 [-0700], Steven Rostedt wrote:
> On Wed, 22 Mar 2017 16:18:43 +0100
> Lionel Debieve wrote:
>
> > Use raw_spin_lock in enable/disable channel as it comes from
> > interrupt context.
> >
> > BUG: sleeping function called from invalid context at
> >
On 2017-03-22 09:05:58 [-0700], Steven Rostedt wrote:
> On Wed, 22 Mar 2017 16:18:43 +0100
> Lionel Debieve wrote:
>
> > Use raw_spin_lock in enable/disable channel as it comes from
> > interrupt context.
> >
> > BUG: sleeping function called from invalid context at
> >
On Thu, 23 Mar 2017, Julia Cartwright wrote:
> On Thu, Mar 23, 2017 at 10:26:49AM +, Lee Jones wrote:
> > On Thu, 23 Mar 2017, Lionel DEBIEVE wrote:
> >
> > > On 03/22/2017 07:47 PM, Julia Cartwright wrote:
> > > > On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
> > > >>
On Thu, 23 Mar 2017, Julia Cartwright wrote:
> On Thu, Mar 23, 2017 at 10:26:49AM +, Lee Jones wrote:
> > On Thu, 23 Mar 2017, Lionel DEBIEVE wrote:
> >
> > > On 03/22/2017 07:47 PM, Julia Cartwright wrote:
> > > > On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
> > > >>
On Wed, 22 Mar 2017, Julia Cartwright wrote:
> On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
> > It will not be threaded because there are IRQF_ONESHOT used.
> >
> > ret = devm_request_threaded_irq(>dev, irq,
> > sti_mbox_irq_handler,
>
On Wed, 22 Mar 2017, Julia Cartwright wrote:
> On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
> > It will not be threaded because there are IRQF_ONESHOT used.
> >
> > ret = devm_request_threaded_irq(>dev, irq,
> > sti_mbox_irq_handler,
>
On Thu, Mar 23, 2017 at 10:26:49AM +, Lee Jones wrote:
> On Thu, 23 Mar 2017, Lionel DEBIEVE wrote:
>
> > On 03/22/2017 07:47 PM, Julia Cartwright wrote:
> > > On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
> > >> On 03/22/2017 01:01 PM, Steven Rostedt wrote:
> > >>> On
On Thu, Mar 23, 2017 at 10:26:49AM +, Lee Jones wrote:
> On Thu, 23 Mar 2017, Lionel DEBIEVE wrote:
>
> > On 03/22/2017 07:47 PM, Julia Cartwright wrote:
> > > On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
> > >> On 03/22/2017 01:01 PM, Steven Rostedt wrote:
> > >>> On
On Thu, 23 Mar 2017, Lionel DEBIEVE wrote:
> On 03/22/2017 07:47 PM, Julia Cartwright wrote:
> > On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
> >> On 03/22/2017 01:01 PM, Steven Rostedt wrote:
> >>> On Wed, 22 Mar 2017 12:37:59 -0500
> >>> Julia Cartwright
On Thu, 23 Mar 2017, Lionel DEBIEVE wrote:
> On 03/22/2017 07:47 PM, Julia Cartwright wrote:
> > On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
> >> On 03/22/2017 01:01 PM, Steven Rostedt wrote:
> >>> On Wed, 22 Mar 2017 12:37:59 -0500
> >>> Julia Cartwright wrote:
> >>>
>
On 03/22/2017 07:47 PM, Julia Cartwright wrote:
> On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
>> On 03/22/2017 01:01 PM, Steven Rostedt wrote:
>>> On Wed, 22 Mar 2017 12:37:59 -0500
>>> Julia Cartwright wrote:
>>>
Which kernel were you testing on, here?
On 03/22/2017 07:47 PM, Julia Cartwright wrote:
> On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
>> On 03/22/2017 01:01 PM, Steven Rostedt wrote:
>>> On Wed, 22 Mar 2017 12:37:59 -0500
>>> Julia Cartwright wrote:
>>>
Which kernel were you testing on, here? From what I
On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
>
> On 03/22/2017 01:01 PM, Steven Rostedt wrote:
> > On Wed, 22 Mar 2017 12:37:59 -0500
> > Julia Cartwright wrote:
> >
> > > Which kernel were you testing on, here? From what I can tell, this
> > > should have
On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
>
> On 03/22/2017 01:01 PM, Steven Rostedt wrote:
> > On Wed, 22 Mar 2017 12:37:59 -0500
> > Julia Cartwright wrote:
> >
> > > Which kernel were you testing on, here? From what I can tell, this
> > > should have been fixed with
On 03/22/2017 01:01 PM, Steven Rostedt wrote:
On Wed, 22 Mar 2017 12:37:59 -0500
Julia Cartwright 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
On 03/22/2017 01:01 PM, Steven Rostedt wrote:
On Wed, 22 Mar 2017 12:37:59 -0500
Julia Cartwright 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
On Wed, 22 Mar 2017 12:37:59 -0500
Julia Cartwright 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
On Wed, 22 Mar 2017 12:37:59 -0500
Julia Cartwright 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
On Wed, Mar 22, 2017 at 04:18:43PM +0100, Lionel Debieve wrote:
> Use raw_spin_lock in enable/disable channel as it comes from
> interrupt context.
>
> BUG: sleeping function called from invalid context at
> kernel/locking/rtmutex.c:995
> in_atomic(): 1, irqs_disabled(): 128, pid: 307, name:
On Wed, Mar 22, 2017 at 04:18:43PM +0100, Lionel Debieve wrote:
> Use raw_spin_lock in enable/disable channel as it comes from
> interrupt context.
>
> BUG: sleeping function called from invalid context at
> kernel/locking/rtmutex.c:995
> in_atomic(): 1, irqs_disabled(): 128, pid: 307, name:
On 03/22/2017 05:05 PM, Steven Rostedt wrote:
> On Wed, 22 Mar 2017 16:18:43 +0100
> Lionel Debieve wrote:
>
>> Use raw_spin_lock in enable/disable channel as it comes from
>> interrupt context.
>>
>> BUG: sleeping function called from invalid context at
>>
On 03/22/2017 05:05 PM, Steven Rostedt wrote:
> On Wed, 22 Mar 2017 16:18:43 +0100
> Lionel Debieve wrote:
>
>> Use raw_spin_lock in enable/disable channel as it comes from
>> interrupt context.
>>
>> BUG: sleeping function called from invalid context at
>> kernel/locking/rtmutex.c:995
>>
On Wed, 22 Mar 2017 16:18:43 +0100
Lionel Debieve wrote:
> Use raw_spin_lock in enable/disable channel as it comes from
> interrupt context.
>
> BUG: sleeping function called from invalid context at
> kernel/locking/rtmutex.c:995
> in_atomic(): 1, irqs_disabled(): 128,
On Wed, 22 Mar 2017 16:18:43 +0100
Lionel Debieve wrote:
> Use raw_spin_lock in enable/disable channel as it comes from
> interrupt context.
>
> BUG: sleeping function called from invalid context at
> kernel/locking/rtmutex.c:995
> in_atomic(): 1, irqs_disabled(): 128, pid: 307, name:
28 matches
Mail list logo