[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140313085341.GC27627@localhost>
Date: Thu, 13 Mar 2014 16:53:41 +0800
From: Fengguang Wu <fengguang.wu@...el.com>
To: Alex Shi <alex.shi@...aro.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [sched/balance] INFO: possible recursive locking detected
On Thu, Mar 13, 2014 at 03:43:11PM +0800, Alex Shi wrote:
> On 03/03/2014 10:25 PM, Fengguang Wu wrote:
> > Greetings,
> >
> > I got the below dmesg and the first bad commit is
> >
> > https://github.com/alexshi/power-scheduling.git single-balance.bak
> > commit 2adc591a5cb6768ad11e63be9011906aa171148d
> > Author: Alex Shi <alex.shi@...aro.org>
> > AuthorDate: Fri Feb 28 15:25:09 2014 +0800
> > Commit: Alex Shi <alex.shi@...aro.org>
> > CommitDate: Sun Mar 2 09:16:38 2014 +0800
> >
> > sched/balance: replace new_idle_balance
> >
> > Curren idle_balance will pull task on half of this group. That is
> > not needed in central balance.
>
>
> Thanks for your testing, Fengguang!
>
> I fixed this issue and updated to the git tree. Is the single-balance
> branch still in your performance radar? :)
Sure, however you know it's costly to queue tests for one single tree.
If your trees are directly based on -rcX kernels, that would cut the
tests required for comparison by half.
Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists