From: David Ahern <dsahern@gmail.com>
To: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: git bisect and perf
Date: Tue, 05 Jun 2012 09:29:10 -0600 [thread overview]
Message-ID: <4FCE25C6.2080601@gmail.com> (raw)
I am trying find out when (ie. which commit) the pebs feature actually
started working on a westmere system and hitting a problem with git-bisect:
# git bisect start arch/x86/kernel/cpu/perf_event*
# git bisect bad v2.6.35
# git bisect good v2.6.38
Some good revs are not ancestor of the bad rev.
git bisect cannot work properly in this case.
Maybe you mistake good and bad revs?
Any ideas on why git bisect would not work?
David
next reply other threads:[~2012-06-05 15:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 15:29 David Ahern [this message]
2012-06-05 15:51 ` git bisect and perf Roland Dreier
2012-06-05 16:56 ` David Ahern
2012-06-05 16:00 ` Peter Zijlstra
2012-06-05 16:05 ` Peter Zijlstra
2012-06-05 17:12 ` David Ahern
2012-06-05 17:35 ` Peter Zijlstra
2012-06-05 23:48 ` David Ahern
2012-06-06 11:46 ` Stephane Eranian
2012-06-05 19:04 ` Stephane Eranian
2012-06-05 19:08 ` David Ahern
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=4FCE25C6.2080601@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/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