public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Anton Blanchard <anton@au1.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/powerpc: Cache the DWARF debug info
Date: Wed, 22 Oct 2014 10:46:59 -0700	[thread overview]
Message-ID: <20141022174659.GA5119@us.ibm.com> (raw)
In-Reply-To: <20141022081730.GB9860@krava.brq.redhat.com>

Jiri Olsa [jolsa@redhat.com] wrote:
| > +			goto out;
| > +		}
| > +		dso->dwfl = dwfl;
| 
| so by this we get powerpc arch code sharing dw handle via dso object,
| but we have lot of generic code too ;-)

Well, this applies to powerpc...

| 
| could you make this happen for unwind__get_entries.. probably
| both sharing same generic code I guess

and unwind_get_entries() applies only to x86 and arm right ? ;-)
Or at least thats what the config/Makefile says.

I can take a look at unwind_get_entries(), but can you please merge
this fix for now, since the current performance is bad?

| 
| thanks,
| jirka


  reply	other threads:[~2014-10-22 17:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 18:56 [PATCH] perf/powerpc: Cache the DWARF debug info Sukadev Bhattiprolu
2014-10-21 19:08 ` Arnaldo Carvalho de Melo
2014-10-22  0:09   ` Sukadev Bhattiprolu
2014-10-22  8:17     ` Jiri Olsa
2014-10-22 17:46       ` Sukadev Bhattiprolu [this message]
2014-10-23 13:37         ` Arnaldo Carvalho de Melo
2014-10-23 14:12           ` Jiri Olsa
2014-10-23 14:26             ` Arnaldo Carvalho de Melo
2014-10-23 15:13               ` Jiri Olsa
2014-10-23 15:33                 ` Arnaldo Carvalho de Melo
2014-10-23 15:39                   ` Jiri Olsa
2014-10-30  6:42     ` [tip:perf/core] perf tools powerpc: " tip-bot for Sukadev Bhattiprolu

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=20141022174659.GA5119@us.ibm.com \
    --to=sukadev@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=anton@au1.ibm.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.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