Re: [PATCH 1/2] kthread: Move prio/affinite change into the newly created thread

2021-03-03 Thread Sebastian Andrzej Siewior
On 2020-11-21 11:55:48 [+0100], Thomas Gleixner wrote: > On Tue, Nov 17 2020 at 13:45, Peter Zijlstra wrote: > > On Tue, Nov 10, 2020 at 12:38:47PM +0100, Sebastian Andrzej Siewior wrote: > > > > Moo... yes this is certainly the easiest solution, because nouveau is a > > horrible rats nest. But

Re: [PATCH 1/2] kthread: Move prio/affinite change into the newly created thread

2020-11-21 Thread Thomas Gleixner
On Tue, Nov 17 2020 at 13:45, Peter Zijlstra wrote: > On Tue, Nov 10, 2020 at 12:38:47PM +0100, Sebastian Andrzej Siewior wrote: > > Moo... yes this is certainly the easiest solution, because nouveau is a > horrible rats nest. But when I spoke to Greg KH about this, he suggested > nouveau ought to

Re: [PATCH 1/2] kthread: Move prio/affinite change into the newly created thread

2020-11-20 Thread Sebastian Andrzej Siewior
On 2020-11-17 13:45:03 [+0100], Peter Zijlstra wrote: > On Tue, Nov 10, 2020 at 12:38:47PM +0100, Sebastian Andrzej Siewior wrote: > > With enabled threaded interrupts the nouveau driver reported the > > following: > > | Chain exists of: > > | >mmap_lock#2 --> >mutex --> _rwsem > > | > > |

Re: [PATCH 1/2] kthread: Move prio/affinite change into the newly created thread

2020-11-17 Thread Peter Zijlstra
On Tue, Nov 10, 2020 at 12:38:47PM +0100, Sebastian Andrzej Siewior wrote: > With enabled threaded interrupts the nouveau driver reported the > following: > | Chain exists of: > | >mmap_lock#2 --> >mutex --> _rwsem > | > | Possible unsafe locking scenario: > | > |CPU0

[PATCH 1/2] kthread: Move prio/affinite change into the newly created thread

2020-11-10 Thread Sebastian Andrzej Siewior
With enabled threaded interrupts the nouveau driver reported the following: | Chain exists of: | >mmap_lock#2 --> >mutex --> _rwsem | | Possible unsafe locking scenario: | |CPU0CPU1 | | lock(_rwsem); |