All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Kan Liang <kan.liang@intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, namhyung@kernel.org,
	ak@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC V8 3/4] perf,tools: per-event callgraph support
Date: Wed, 5 Aug 2015 09:21:59 +0200	[thread overview]
Message-ID: <20150805072112.GC20530@krava.redhat.com> (raw)
In-Reply-To: <1438677022-34296-4-git-send-email-kan.liang@intel.com>

On Tue, Aug 04, 2015 at 04:30:21AM -0400, Kan Liang wrote:

SNIP

> +
> +	/* User explicitly set per-event callgraph, clear the old setting and reset. */
> +	if ((callgraph_buf != NULL) || (dump_size > 0)) {
> +
> +		/* parse callgraph parameters */
> +		if (callgraph_buf != NULL) {
> +			if (!strcmp(callgraph_buf, "no")) {
> +				param.enabled = false;
> +				param.record_mode = CALLCHAIN_NONE;
> +			} else {
> +				param.enabled = true;
> +				if (parse_callchain_record_opt(callgraph_buf, &param)) {
> +					pr_err("per-event callgraph setting for %s failed. "
> +					       "Apply callgraph global setting for it\n",
> +					       evsel->name);
> +					return;
> +				}
> +			}
> +		}
> +		if (dump_size > 0)
> +			param.dump_size = dump_size;

the parse_callchain_record_opt does some rounding on the stack size value
via the get_stack_size function, so following command like does not fail:

  $ perf record --call-graph='dwarf,819' ls

while the term syntax fails:
  $ perf record -e 'cpu/cpu-cycles,call-graph=dwarf,stack-size=819/

  Error:
  The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event (cpu/cpu-cycles,time=0,call-graph=dwarf,stack-size=819/).
  /bin/dmesg may provide additional information.
  No CONFIG_PERF_EVENTS=y kernel support configured?


jirka

  reply	other threads:[~2015-08-05  7:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04  8:30 [PATCH RFC V8 0/4] per event callgraph and time support Kan Liang
2015-08-04  8:30 ` [PATCH RFC V8 1/4] perf,tools: per-event " Kan Liang
2015-08-05  7:18   ` Jiri Olsa
2015-08-06  7:02   ` [tip:perf/core] perf tools: Per-event " tip-bot for Kan Liang
2015-08-04  8:30 ` [PATCH RFC V8 2/4] perf,tools: refine parse/config callchain functions Kan Liang
2015-08-05  7:18   ` Jiri Olsa
2015-08-06  7:03   ` [tip:perf/core] perf tools: Refine parse/ config " tip-bot for Kan Liang
2015-08-04  8:30 ` [PATCH RFC V8 3/4] perf,tools: per-event callgraph support Kan Liang
2015-08-05  7:21   ` Jiri Olsa [this message]
2015-08-05  7:28   ` Jiri Olsa
2015-08-05 15:45     ` Liang, Kan
2015-08-06 18:55       ` Arnaldo Carvalho de Melo
2015-08-04  8:30 ` [PATCH RFC V8 4/4] perf,tests: Add tests to callgraph and time parse Kan Liang

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=20150805072112.GC20530@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@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 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.