From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Jirka Hladky <jhladky@redhat.com>, Peter Zijlstra <peterz@infradead.org>
Cc: Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
"kkolakow@redhat.com" <kkolakow@redhat.com>
Subject: Re: sched : performance regression 24% between 4.4rc4 and 4.3 kernel
Date: Fri, 18 Dec 2015 03:49:36 +0100 [thread overview]
Message-ID: <1450406976.3942.21.camel@gmail.com> (raw)
In-Reply-To: <CAE4VaGAbS6AmTV99nmc5+06D0rMbY+uh9=O_NR1EC2Cxnf5SjA@mail.gmail.com>
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
prev parent reply other threads:[~2015-12-18 2:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 14:17 sched : performance regression 24% between 4.4rc4 and 4.3 kernel Jirka Hladky
2015-12-12 7:04 ` Mike Galbraith
2015-12-12 14:16 ` Jirka Hladky
2015-12-12 14:37 ` Mike Galbraith
2015-12-15 0:02 ` Jirka Hladky
2015-12-15 0:04 ` Jirka Hladky
[not found] ` <CAE4VaGCgAvvQXDsv=Gn8B0JtTzCnXe0oP63HLQWSCyY_QNOB7g@mail.gmail.com>
2015-12-15 2:12 ` Rik van Riel
2015-12-15 8:49 ` Jirka Hladky
2015-12-16 12:56 ` Jirka Hladky
2015-12-16 13:50 ` Peter Zijlstra
2015-12-16 17:04 ` Jirka Hladky
[not found] ` <CAE4VaGD49UAsBJn3jgg0kREWqjYz8UnvWOi8zU4d5HgNgNS-sQ@mail.gmail.com>
2015-12-17 15:43 ` Jirka Hladky
2015-12-18 2:49 ` Mike Galbraith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1450406976.3942.21.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=jhladky@redhat.com \
--cc=kkolakow@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).