public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
	Namhyung Kim <namhyung.kim@lge.com>,
	LKML <linux-kernel@vger.kernel.org>, Arun Sharma <asharma@fb.com>,
	David Ahern <dsahern@gmail.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Jean Pihet <jean.pihet@linaro.org>
Subject: Re: [PATCH v2 1/2] perf callchain: Create an address space per thread
Date: Tue, 30 Sep 2014 10:17:34 -0300	[thread overview]
Message-ID: <20140930131734.GA2799@kernel.org> (raw)
In-Reply-To: <87vbo5hc3a.fsf@sejong.aot.lge.com>

Em Tue, Sep 30, 2014 at 03:11:21PM +0900, Namhyung Kim escreveu:
> 
> On Mon, 29 Sep 2014 10:34:52 +0200, Jiri Olsa wrote:
> > On Mon, Sep 29, 2014 at 01:58:11PM +0900, Namhyung Kim wrote:
> >> @@ -37,6 +38,9 @@ struct thread *thread__new(pid_t pid, pid_t tid)
> >>  		thread->cpu = -1;
> >>  		INIT_LIST_HEAD(&thread->comm_list);

> >> +		if (unwind__prepare_access(thread) < 0)
> >> +			goto err_thread;

> > So this is something we need to do only for DWARF unwind via libunwind.
> > Do we want some condition to bypass this in for the rest of the cases?
 
> Ah, you're right, we need to check that before doing this.

> > I think we could check for symbol_conf.use_callchain and for the
> > PERF_SAMPLE_REGS_USER|PERF_SAMPLE_STACK_USER sample types in evlist,
> > something like:

> >   bool has_dwarf_data_for_callchains = symbol_conf.use_callchain && evlist_sample_type_has(evlist, PERF_SAMPLE_REGS_USER|PERF_SAMPLE_STACK_USER)

> Hmm.. it seems that it's hard to get the evlist at this point.  Maybe we
> need to add a field in the symbol_conf or a global variable.. :/

Please don't export evlist in a global way, just set some flag on
symbol_conf.

At some point we need to ditch even symbol_conf :-\

- Arnaldo

      parent reply	other threads:[~2014-09-30 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29  4:58 [PATCH v2 1/2] perf callchain: Create an address space per thread Namhyung Kim
2014-09-29  4:58 ` [PATCH v2 2/2] perf callchain: Use global caching provided by libunwind Namhyung Kim
2014-09-29  8:34 ` [PATCH v2 1/2] perf callchain: Create an address space per thread Jiri Olsa
2014-09-30  6:11   ` Namhyung Kim
2014-09-30  7:16     ` Jiri Olsa
2014-09-30 13:17     ` Arnaldo Carvalho de Melo [this message]

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=20140930131734.GA2799@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=asharma@fb.com \
    --cc=dsahern@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=jean.pihet@linaro.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=namhyung@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox