perf report: Amend documentation about max_stack and synthesized callchains
authorAdrian Hunter <adrian.hunter@intel.com>
Tue, 29 Sep 2015 08:52:37 +0000 (11:52 +0300)
committerArnaldo Carvalho de Melo <acme@redhat.com>
Wed, 30 Sep 2015 21:34:26 +0000 (18:34 -0300)
commit40862a7b793945c7080d1566ca3dc6249f3c6354
treed06d9f4296703f5bfd22eba6d73ecab261c45330
parentb7f9ff5654d53fa47e0b5ff20f834f3e7a611846
perf report: Amend documentation about max_stack and synthesized callchains

The --max_stack option was added as an optimization to reduce processing time,
so people specifying --max-stack might get a increased processing time if
combined with synthesized callchains, but otherwise no real harm.

A warning about setting both --max_stack and the synthesized callchains max
depth seems like overkill.  Amend the documentation.

Reported-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Link: http://lkml.kernel.org/r/560A5155.4060105@intel.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
tools/perf/Documentation/perf-report.txt