All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Anton Blanchard <anton@samba.org>
Cc: Eric B Munson <ebmunson@us.ibm.com>,
	mingo@elte.hu, a.p.zijlstra@chello.nl, paulus@samba.org,
	linux-kernel@vger.kernel.org, amodra@gmail.com
Subject: Re: [PATCH] perf lookup of ppc64 symbols
Date: Thu, 17 Jun 2010 12:17:05 -0300	[thread overview]
Message-ID: <20100617151705.GD4217@ghostprotocols.net> (raw)
In-Reply-To: <20100617144608.GS28295@kryten>

Em Fri, Jun 18, 2010 at 12:46:08AM +1000, Anton Blanchard escreveu:
> 
> Hi,
> 
> > Currently symbol resolution does not work for 64-bit programs
> > using perf.  For this to work perf needs to lookup symbol names in
> > the OPD.  This patch adds this functionality.  The OPD data is
> > used to find symbol names when available.
> 
> To clarify, this is an issue with 64bit architectures that use function
> descriptors (eg ppc64). The problem is that a symbol doesn't point to a text
> address, it points to a data area that contains (amongst other things) a
> pointer to the text address.
> 
> We look for a section called ".opd" which is the function descriptor
> area. To create the full symbol table, when we see a symbol in the function
> descriptor section we load the first pointer and use that as the text
> address. The only tricky part here is working out which section the
> text address is in. Right now we have a loop which is sub optimal:

I'll update the comment in Eric's patch and apply this to perf/core, for
.36, we can optimize this later, correctness first :-)

- Arnaldo

  reply	other threads:[~2010-06-17 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14 13:56 [PATCH] perf lookup of ppc64 symbols Eric B Munson
2010-06-17 14:46 ` Anton Blanchard
2010-06-17 15:17   ` Arnaldo Carvalho de Melo [this message]
2010-06-17 15:19     ` Arnaldo Carvalho de Melo
2010-06-18 10:16 ` [tip:perf/core] perf symbols: Function descriptor symbol lookup tip-bot for Eric B Munson

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=20100617151705.GD4217@ghostprotocols.net \
    --to=acme@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=amodra@gmail.com \
    --cc=anton@samba.org \
    --cc=ebmunson@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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 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.