Re: sched : performance regression 24% between 4.4rc4 and 4.3 kernel

[Mike Galbraith]

On Thu, 2015-12-17 at 16:43 +0100, Jirka Hladky wrote:
> Hi Peter,
> 
> I'm not sure how to do the bisecting and avoid landing at:
> 
> [2a595721a1fa6b684c1c818f379bef834ac3d65e] sched/numa: Convert
> sched_numa_balancing to a static_branch
> 
> I have redone the bisecting but I have landed again at this commit.
> Can you please help me to identify the commit which has fixed for
> 2a595721a1fa6b684c1c818f379bef834ac3d65e ? I think I will need to
> start the bisecting from there.

One way...

Put b52da86e0ad58f096710977fcda856fd84da9233 in quilt queue, try to
quilt push before each build, ignoring whether it applies or not.  If
it does apply, quilt pop before saying git bisect [good/bad] lest git
refuse to play due to you mucking about with its source its source.

	-Mike

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/