From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
Anton Blanchard <anton@au1.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/powerpc: Cache the DWARF debug info
Date: Thu, 23 Oct 2014 12:33:22 -0300 [thread overview]
Message-ID: <20141023153322.GH14687@kernel.org> (raw)
In-Reply-To: <20141023151306.GA25215@krava.brq.redhat.com>
Em Thu, Oct 23, 2014 at 05:13:06PM +0200, Jiri Olsa escreveu:
> On Thu, Oct 23, 2014 at 11:26:34AM -0300, Arnaldo Carvalho de Melo wrote:
> > That is why I thought it would be a compromise to put what he did, it
> > would not make the existing situation that much worse, work needs to be
> > done in this area :-\
> I think we just need to put that libdw handle into dso object
> as I suggested above
Isn't it there already?
The patch does:
+++ b/tools/perf/util/dso.h
@@ -127,6 +127,7 @@ struct dso {
const char *long_name;
u16 long_name_len;
u16 short_name_len;
+ void *dwfl; /* DWARF debug info */
----------
What you want, on top of that, at a minimum, we somehow limit the number
of simultaneously dwfl_begin()'ed DSOs, right?
- Arnaldo
next prev parent reply other threads:[~2014-10-23 15:33 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
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 [this message]
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=20141023153322.GH14687@kernel.org \
--to=acme@kernel.org \
--cc=anton@au1.ibm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sukadev@linux.vnet.ibm.com \
/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.