[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANRm+Cx9w21=uyP52SCw=P726iLUs7WC_kX5sJ4+UDJB_a2maQ@mail.gmail.com>
Date: Sun, 19 Mar 2017 09:55:14 +0800
From: Wanpeng Li <kernellwp@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: kernel test robot <fengguang.wu@...el.com>, LKP <lkp@...org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>, wfg@...ux.intel.com
Subject: Re: [sched/core] 8a8c69c327: WARNING: CPU: 0 PID: 8 at
kernel/locking/lockdep.c:3548 lock_release
2017-03-17 22:13 GMT+08:00 Peter Zijlstra <peterz@...radead.org>:
> On Fri, Mar 17, 2017 at 03:09:09PM +0100, Peter Zijlstra wrote:
>> On Fri, Mar 17, 2017 at 09:24:11PM +0800, Wanpeng Li wrote:
>> > I have another version of patch which utilizes raw_spin_lock_irqsave()
>> > instead of rq_lock_irqsave() in __balance_callback() as before, which
>> > one do you like, Peterz?
>>
>> Hurm.. the raw_spin_lock_irqsave() one I suspect. No point in pinning
>> and then unpinning.
>
> Took your other version and edited that to make it do this.
Please refer to https://lkml.org/lkml/2017/3/17/704 :)
Regards,
Wanpeng Li
Powered by blists - more mailing lists