Re: [PATCH] fix might sleep oops in irq affinity callback hook

[PATCH] fix might sleep oops in irq affinity callback hook · Joe Korty <hidden> · 2013-08-20
Re: [PATCH] fix might sleep oops in irq affinity callback hook · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2013-08-21
Re: [PATCH] fix might sleep oops in irq affinity callback hook · Joe Korty <hidden> · 2013-08-21
Re: [PATCH] fix might sleep oops in irq affinity callback hook · Joe Korty <hidden> · 2013-08-22
Re: [PATCH] fix might sleep oops in irq affinity callback hook · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2013-08-23
Re: [PATCH] fix might sleep oops in irq affinity callback hook · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2013-08-29
Re: [PATCH] fix might sleep oops in irq affinity callback hook · Joe Korty <hidden> · 2013-08-30

From: Joe Korty <hidden>
Date: 2013-08-21 21:09:41

On Wed, Aug 21, 2013 at 11:53:47AM -0400, Sebastian Andrzej Siewior wrote:

Joe could you please test this one? In 3.10 we have one user of
__irq_set_affinity_locked() and we might get more.

Hi Sebastian,
I backported the patch to 3.6.11.6-rt38 and added a few printk's so that
when daemon started I would see that and when each affinity hook was
executed I would see that too.

The system came up and the printk for daemon start showed up near where
the sfc driver started, but no affinity action printk appeared.  Thus
the patch as written does not seem to work.

Joe

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help