From: Peter Zijlstra <peterz@infradead.org>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Hagen Paul Pfeifer <hagen@jauu.net>,
Mike Galbraith <efault@gmx.de>, Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL 0/4] perf/annotate loop detection V2, fixes
Date: Fri, 27 Apr 2012 17:48:57 +0200 [thread overview]
Message-ID: <1335541737.2463.135.camel@laptop> (raw)
In-Reply-To: <20120427153119.GC27997@infradead.org>
On Fri, 2012-04-27 at 12:31 -0300, Arnaldo Carvalho de Melo wrote:
> > So the forward conditional jumps get moved by one character to
> > the right and get prefixed with '.', which has the following
> > effects:
> >
> > - the flow of all the 'other', register modifying and loop
> > instructions can be seen more clearly
> >
> > - the 'exception' forward conditional jumps get moved into the
> > visual background, slightly.
> >
> > - blocks of instructions with no branches amongst them are more
> > clearly visible.
> >
> > If '.' is too aggressive or too confusing then some other
> > (possibly graphical) character could be used as well?
>
> Yeah, there are some unused graphical chars. But perhaps we should just
> use ↓ again?
>
> 0.00 │┌─→ c0: cmp %rax,%rbx
> 0.00 ││ mov %rax,%rcx
> 0.00 ││ ↓ ↓je 5dd
> 0.00 ││ cc: test %rcx,%rcx
> 0.00 ││ ↓ ↓je da
> 0.00 ││ mov 0x8(%rcx),%esi
> 0.00 ││ shr $0x4,%esi
> 0.00 ││ sub $0x2,%esi
> 0.00 ││ da: mov %rcx,0x10(%rbx)
> 0.00 ││ mov %rcx,%rax
> 0.00 ││ cmpl $0x0,%fs:0x18
> 0.00 ││ ↓ ↓je ed
> 0.00 ││ lock cmpxchg %rbx,(%rdx)
> 0.00 ││ cmp %rax,%rcx
> ││
> 0.00 │└──────↑ } jne c0
>
> Does it still stands out? I think so, we expect a letter there,
> something very different is there, matching the other down arrowsome
> columns to the left.
That just looks daft.. what's wrong with the single up/down arrow?
Also, can we keep all this on the list please?
next prev parent reply other threads:[~2012-04-27 15:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 15:06 [GIT PULL 0/4] perf/annotate loop detection V2, fixes Arnaldo Carvalho de Melo
2012-04-26 15:06 ` [PATCH 1/4] perf annotate browser: Handle NULL jump targets Arnaldo Carvalho de Melo
2012-04-26 15:06 ` [PATCH 2/4] perf annotate: Disambiguage offsets and addresses in operands Arnaldo Carvalho de Melo
2012-04-26 15:06 ` [PATCH 3/4] perf annotate: Mark jump instructions with no offset Arnaldo Carvalho de Melo
2012-04-26 15:06 ` [PATCH 4/4] perf annotate browser: Don't draw jump connectors for out of function jumps Arnaldo Carvalho de Melo
2012-04-27 7:21 ` [GIT PULL 0/4] perf/annotate loop detection V2, fixes Ingo Molnar
2012-04-27 8:06 ` Ingo Molnar
2012-04-27 15:31 ` Arnaldo Carvalho de Melo
2012-04-27 15:48 ` Peter Zijlstra [this message]
2012-04-27 16:07 ` Arnaldo Carvalho de Melo
2012-04-27 16:20 ` Peter Zijlstra
2012-04-27 18:09 ` Arnaldo Carvalho de Melo
2012-04-27 15:16 ` Arnaldo Carvalho de Melo
2012-04-27 16:35 ` Linus Torvalds
2012-04-27 16:46 ` Arnaldo Carvalho de Melo
2012-04-27 17:12 ` Linus Torvalds
2012-04-27 18:03 ` Arnaldo Carvalho de Melo
2012-04-27 18:23 ` Linus Torvalds
2012-04-27 19:17 ` Arnaldo Carvalho de Melo
2012-04-28 13:38 ` Arnaldo Carvalho de Melo
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=1335541737.2463.135.camel@laptop \
--to=peterz@infradead.org \
--cc=acme@infradead.org \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=hagen@jauu.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.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