From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>, Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [GIT PULL 0/8] Annotation weekly ponies delivery
Date: Sat, 12 May 2012 18:25:31 -0300 [thread overview]
Message-ID: <20120512212531.GC20057@infradead.org> (raw)
In-Reply-To: <CA+55aFxeqrCj71fSe2r9kwzyO9q2BT9A89f7nLUgbrTG_uPP2g@mail.gmail.com>
Em Sat, May 12, 2012 at 01:40:07PM -0700, Linus Torvalds escreveu:
> On Sat, May 12, 2012 at 12:52 PM, Arnaldo Carvalho de Melo
> <acme@infradead.org> wrote:
> >
> > Arjan & Linus Annotation Edition
>
> I pulled this into my current git tree just for testing.
>
> It's horribly broken, but it's not the annotation that is broken.
>
> The whole "-e cycles:pp" doesn't work any more. I don't get any nice
> PEBS information, I get the totally useless irq-based profiling.
> I don't think this has anything to do with your changes, but I thought
> I'd report it anyway. Something in 'perf' land is broken.
Didn't notice it, but then I'm not updating the kernel that frequently,
will check on this Sandy Bridge nobo (i7-2920XM).
- Arnaldo
next prev parent reply other threads:[~2012-05-12 21:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 19:52 [GIT PULL 0/8] Annotation weekly ponies delivery Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 1/8] perf annotate: Use raw form for register indirect call instructions Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 2/8] perf annotate: Resolve symbols using objdump comment Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 3/8] perf annotate: Resolve symbols using objdump comment for single op ins Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 4/8] perf annotate: Augment lock instruction output Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 5/8] perf annotate: Introduce ->free() method in ins_ops Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 6/8] perf annotate browser: Count the numbers of jump sources to a target Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 7/8] perf annotate browser: Show 'jumpy' functions Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 8/8] perf annotate browser: Add key bindings help window Arnaldo Carvalho de Melo
2012-05-12 20:40 ` [GIT PULL 0/8] Annotation weekly ponies delivery Linus Torvalds
2012-05-12 21:25 ` Arnaldo Carvalho de Melo [this message]
2012-05-12 22:29 ` Linus Torvalds
2012-05-14 7:05 ` Ingo Molnar
2012-05-14 11:13 ` Peter Zijlstra
2012-05-14 11:55 ` Ingo Molnar
2012-05-14 15:06 ` Namhyung Kim
2012-05-15 4:48 ` Namhyung Kim
2012-05-15 10:32 ` Peter Zijlstra
2012-05-15 14:44 ` Namhyung Kim
2012-05-15 17:07 ` Peter Zijlstra
2012-05-16 5:57 ` Namhyung Kim
2012-05-16 8:19 ` Namhyung Kim
2012-05-17 0:13 ` Namhyung Kim
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=20120512212531.GC20057@infradead.org \
--to=acme@infradead.org \
--cc=arjan@infradead.org \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).