public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Anton Blanchard <anton@samba.org>,
	Neil Horman <nhorman@tuxdriver.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	<linux-kernel@vger.kernel.org>, Paul Mackerras <paulus@samba.org>,
	<linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] module: ppc64 module CRC relocation fix causes perf issues
Date: Wed, 24 Jul 2013 14:22:53 -0500	[thread overview]
Message-ID: <1374693773.15592.59@snotra> (raw)
In-Reply-To: <20130723133032.GB31944@concordia> (from michael@ellerman.id.au on Tue Jul 23 08:30:32 2013)

On 07/23/2013 08:30:32 AM, Michael Ellerman wrote:
> On Fri, Jul 19, 2013 at 05:59:30PM -0500, Scott Wood wrote:
> > On 07/17/2013 11:00:45 PM, Anton Blanchard wrote:
> > >
> > >Hi Scott,
> > >
> > >> What specifically should I do to test it?
> > >
> > >Could you double check perf annotate works? I'm 99% sure it will  
> but
> > >that is what was failing on ppc64.
> >
> > I'm not really sure what it's supposed to look like when "perf
> > annotate" works.  It spits a bunch of unreadable[1]
> > dark-blue-on-black assembly code at me, all with "0.00 :" in the
> > left column.
> >
> > Oh, wait -- some lines have "100.00 : " on the left, in
> > even-more-unreadable dark-red-on-black.
> >
> > Apart from the annoying colors, is there anything specific I should
> > be looking for?  Some sort of error message, or output that actually
> > makes sense?
> 
> The colours look fine on my terminal, so I don't know what you've done
> there.

It probably looks better if the terminal is configured to have a light  
background (which of course makes some other programs look worse), or  
(as I noted) if you've got your monitor set to be very bright.  I now  
see that xfce4-terminal lets me redefine the standard colors, though,  
so that should help.

> If you care you can use "--stdio" to use the plainer interface,
> though it still uses colours.
> 
> That output looks fine in terms of the bug Anton was chasing. As far  
> as
> only ever hitting one instruction that does look weird.

OK.  I'll add "investigate weird e500 perf annotate results" to the  
TODO list...

-Scott

  reply	other threads:[~2013-07-24 19:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15  4:04 [PATCH] module: ppc64 module CRC relocation fix causes perf issues Anton Blanchard
2013-07-15  4:39 ` Rusty Russell
2013-07-15  8:47 ` Benjamin Herrenschmidt
2013-07-16 22:40   ` Scott Wood
2013-07-17  0:04     ` Benjamin Herrenschmidt
2013-07-17  0:08       ` Scott Wood
2013-07-18  4:00         ` Anton Blanchard
2013-07-19 22:59           ` Scott Wood
2013-07-23 13:30             ` Michael Ellerman
2013-07-24 19:22               ` Scott Wood [this message]
2013-07-24 22:34             ` Anton Blanchard
2013-07-24 23:14               ` Benjamin Herrenschmidt
2013-07-25 13:02                 ` Neil Horman
2013-07-26  1:19                   ` Anton Blanchard
2013-07-26 13:11                     ` Neil Horman

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=1374693773.15592.59@snotra \
    --to=scottwood@freescale.com \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=nhorman@tuxdriver.com \
    --cc=paulus@samba.org \
    --cc=rusty@rustcorp.com.au \
    /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