Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966049AbbLRCtl (ORCPT ); Thu, 17 Dec 2015 21:49:41 -0500 Received: from mail-wm0-f43.google.com ([74.125.82.43]:35901 "EHLO mail-wm0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751991AbbLRCtk (ORCPT ); Thu, 17 Dec 2015 21:49:40 -0500 Message-ID: <1450406976.3942.21.camel@gmail.com> Subject: Re: sched : performance regression 24% between 4.4rc4 and 4.3 kernel From: Mike Galbraith To: Jirka Hladky , Peter Zijlstra Cc: Rik van Riel , linux-kernel@vger.kernel.org, Ingo Molnar , "kkolakow@redhat.com" Date: Fri, 18 Dec 2015 03:49:36 +0100 In-Reply-To: References: <1449903863.9638.8.camel@gmail.com> <1449931045.7411.8.camel@gmail.com> <566F7715.3020905@redhat.com> <20151216135001.GO6357@twins.programming.kicks-ass.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1027 Lines: 27 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/