mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Stanislav Fomichev <stfomichev@yandex-team.ru>
Cc: a.p.zijlstra@chello.nl, paulus@samba.org, mingo@redhat.com,
	acme@ghostprotocols.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] perf timechart: add backtrace support
Date: Tue, 29 Oct 2013 17:41:54 +0900	[thread overview]
Message-ID: <87d2mo5uzx.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1382439412-23713-7-git-send-email-stfomichev@yandex-team.ru> (Stanislav Fomichev's message of "Tue, 22 Oct 2013 14:56:52 +0400")

On Tue, 22 Oct 2013 14:56:52 +0400, Stanislav Fomichev wrote:
> Add -g flag to `perf timechart record` which saves callchain info in
> the perf.data.
> When generating SVG, add backtrace information to the figure details,
> so now it's possible to see which code path woke up the task and why some
> task went to sleep.

[SNIP]

> +static const char *cat_backtrace(union perf_event *event,
> +				 struct perf_sample *sample,
> +				 struct machine *machine)
> +{
> +	struct addr_location al;
> +	unsigned int i;
> +	char *p = NULL;
> +	size_t p_len;
> +	u8 cpumode = PERF_RECORD_MISC_USER;
> +	struct addr_location tal;
> +	struct ip_callchain *chain = sample->callchain;
> +	FILE *f = open_memstream(&p, &p_len);

It is safer to check the return value.

> +
> +	if (!chain)
> +		return NULL;
> +
> +	if (perf_event__preprocess_sample(event, machine, &al, sample) < 0) {
> +		fprintf(stderr, "problem processing %d event, skipping it.\n",
> +			event->header.type);
> +		return NULL;
> +	}

Above two returns should close 'f'.

> +
> +	for (i = 0; i < chain->nr; i++) {
> +		u64 ip;
> +
> +		if (callchain_param.order == ORDER_CALLEE)
> +			ip = chain->ips[i];
> +		else
> +			ip = chain->ips[chain->nr - i - 1];

The ip might carry context information rather than the actual
instruction pointer.  Please see machine__resolve_callchain_sample().

> +
> +		tal.filtered = false;
> +		thread__find_addr_location(al.thread, machine, cpumode,
> +					   MAP__FUNCTION, ip, &tal);
> +
> +		if (tal.sym)
> +			fprintf(f, "..... %016" PRIx64 " %s\n", ip,
> +				tal.sym->name);
> +		else
> +			fprintf(f, "..... %016" PRIx64 "\n", ip);
> +	}
> +
> +	fclose(f);
> +
> +	return p;
> +}
> +
>  typedef int (*tracepoint_handler)(struct perf_evsel *evsel,
> -				  struct perf_sample *sample);
> +				  struct perf_sample *sample,
> +				  const char *backtrace);
>  
>  static int process_sample_event(struct perf_tool *tool __maybe_unused,
>  				union perf_event *event __maybe_unused,
> @@ -485,7 +545,8 @@ static int process_sample_event(struct perf_tool *tool __maybe_unused,
>  
>  	if (evsel->handler.func != NULL) {
>  		tracepoint_handler f = evsel->handler.func;
> -		return f(evsel, sample);
> +		return f(evsel, sample,
> +			 cat_backtrace(event, sample, machine));
>  	}
>  
>  	return 0;
> @@ -493,7 +554,8 @@ static int process_sample_event(struct perf_tool *tool __maybe_unused,
>  
>  static int
>  process_sample_cpu_idle(struct perf_evsel *evsel __maybe_unused,
> -			struct perf_sample *sample)
> +			struct perf_sample *sample,
> +			const char *backtrace __maybe_unused)
>  {
>  	struct power_processor_entry *ppe = sample->raw_data;
>  
> @@ -506,7 +568,8 @@ process_sample_cpu_idle(struct perf_evsel *evsel __maybe_unused,
>  
>  static int
>  process_sample_cpu_frequency(struct perf_evsel *evsel __maybe_unused,
> -			     struct perf_sample *sample)
> +			     struct perf_sample *sample,
> +			     const char *backtrace __maybe_unused)
>  {
>  	struct power_processor_entry *ppe = sample->raw_data;
>  
> @@ -516,28 +579,31 @@ process_sample_cpu_frequency(struct perf_evsel *evsel __maybe_unused,
>  
>  static int
>  process_sample_sched_wakeup(struct perf_evsel *evsel __maybe_unused,
> -			    struct perf_sample *sample)
> +			    struct perf_sample *sample,
> +			    const char *backtrace __maybe_unused)

You don't need to add __maybe_unused if it's used. :)


>  {
>  	struct trace_entry *te = sample->raw_data;
>  
> -	sched_wakeup(sample->cpu, sample->time, sample->pid, te);
> +	sched_wakeup(sample->cpu, sample->time, sample->pid, te, backtrace);
>  	return 0;
>  }
>  
[SNIP]

> @@ -1166,6 +1255,7 @@ int cmd_timechart(int argc, const char **argv,
>  		     "record power data only", parse_power),
>  	OPT_CALLBACK_NOOPT('T', "tasks-only", NULL, NULL,
>  		     "record processes data only", parse_tasks),
> +	OPT_BOOLEAN('g', "callchain", &with_backtrace, "record callchain"),

Please update the doc also.

Thanks,
Namhyung


>  	OPT_END()
>  	};
>  	const char * const record_usage[] = {

      reply	other threads:[~2013-10-29  8:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22 10:56 [PATCH 0/6] perf timechart improvements Stanislav Fomichev
2013-10-22 10:56 ` [PATCH 1/6] perf timechart: always try to print at least 15 tasks Stanislav Fomichev
2013-10-29  7:50   ` Namhyung Kim
2013-10-29  9:24     ` Stanislav Fomichev
2013-11-01  6:06       ` Namhyung Kim
2013-10-22 10:56 ` [PATCH 2/6] perf timechart: use proc_num to implement --power-only Stanislav Fomichev
2013-10-29  8:03   ` Namhyung Kim
2013-10-29  9:28     ` Stanislav Fomichev
2013-11-01  6:07       ` Namhyung Kim
2013-10-22 10:56 ` [PATCH 3/6] perf timechart: add support for displaying only tasks related data Stanislav Fomichev
2013-10-29  8:10   ` Namhyung Kim
2013-10-29  9:33     ` Stanislav Fomichev
2013-11-01  6:10       ` Namhyung Kim
2013-10-22 10:56 ` [PATCH 4/6] perf timechart: group figures and add title with details Stanislav Fomichev
2013-10-29  8:15   ` Namhyung Kim
2013-10-29  9:35     ` Stanislav Fomichev
2013-10-22 10:56 ` [PATCH 5/6] perf timechart: add support for -P and -T in timechart recording Stanislav Fomichev
2013-10-29  8:27   ` Namhyung Kim
2013-10-29  9:51     ` Stanislav Fomichev
2013-10-22 10:56 ` [PATCH 6/6] perf timechart: add backtrace support Stanislav Fomichev
2013-10-29  8:41   ` Namhyung Kim [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=87d2mo5uzx.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=stfomichev@yandex-team.ru \
    /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

all inboxes | Powered by JetHome®