From: Corey Ashford <cjashfor@linux.vnet.ibm.com>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
mingo@elte.hu, "Robert Richter" <robert.richter@amd.com>
Subject: Re: [BUG] perf sched broken
Date: Wed, 12 Jan 2011 11:41:55 -0800 [thread overview]
Message-ID: <4D2E0403.7080300@linux.vnet.ibm.com> (raw)
In-Reply-To: <AANLkTim=jawJyBj0iFd0r4-LCKzvjFW+NddzJMD5GUB9@mail.gmail.com>
On 01/12/2011 01:29 AM, Stephane Eranian wrote:
> Hi,
>
> I am trying to use perf sched from tip-x86 but it fails for all my attempts.
So far I have been unsuccessful in reproducing this problem, but I
suspect that I have the wrong git tree or branch. The git tree I've
cloned is:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
I've tried the branches master, x86/urgent, and x86-urgent-for-linus.
All of those produce correct results, as far as I can tell.
Which tree / branch should I be using?
- Corey
next prev parent reply other threads:[~2011-01-12 19:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 9:29 [BUG] perf sched broken Stephane Eranian
2011-01-12 12:11 ` Arnaldo Carvalho de Melo
2011-01-12 19:10 ` Corey Ashford
2011-01-12 19:41 ` Corey Ashford [this message]
2011-01-12 19:52 ` Stephane Eranian
2011-01-12 20:22 ` Corey Ashford
2011-01-12 22:35 ` Corey Ashford
2011-01-12 22:38 ` Stephane Eranian
2011-01-13 1:53 ` Corey Ashford
2011-01-13 13:20 ` Arnaldo Carvalho de Melo
2011-01-14 7:25 ` [tip:perf/urgent] perf sched: Fix list of events, dropping unsupported ':r' modifier tip-bot for Stephane Eranian
2011-08-03 10:59 ` Peter Zijlstra
2011-08-03 11:37 ` Frederic Weisbecker
2011-08-03 11:42 ` Peter Zijlstra
2011-08-03 11:57 ` Frederic Weisbecker
2011-08-03 12:05 ` Peter Zijlstra
2011-08-03 12:11 ` Frederic Weisbecker
2011-08-03 12:18 ` Peter Zijlstra
2011-08-03 17:06 ` Arnaldo Carvalho de Melo
2011-08-03 19:49 ` Peter Zijlstra
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=4D2E0403.7080300@linux.vnet.ibm.com \
--to=cjashfor@linux.vnet.ibm.com \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.