mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-08-22 17:01:14 +00:00
perf tools: Fix foolproof typo
In the context of LBR stitching documentation. Signed-off-by: Ian Rogers <irogers@google.com> Acked-by: Kan Liang <kan.liang@linux.intel.com> Cc: Adrian Hunter <adrian.hunter@intel.com> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com> Cc: Ali Saidi <alisaidi@amazon.com> Cc: Ingo Molnar <mingo@redhat.com> Cc: James Clark <james.clark@arm.com> Cc: Jiri Olsa <jolsa@kernel.org> Cc: Leo Yan <leo.yan@linaro.org> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Namhyung Kim <namhyung@kernel.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Ravi Bangoria <ravi.bangoria@amd.com> Cc: Sandipan Das <sandipan.das@amd.com> Link: https://lore.kernel.org/r/20230119201036.156441-1-irogers@google.com Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
This commit is contained in:
parent
df8aeaefea
commit
4cbd5334ff
4 changed files with 4 additions and 4 deletions
|
@ -121,7 +121,7 @@ REPORT OPTIONS
|
||||||
perf c2c record --call-graph lbr.
|
perf c2c record --call-graph lbr.
|
||||||
Disabled by default. In common cases with call stack overflows,
|
Disabled by default. In common cases with call stack overflows,
|
||||||
it can recreate better call stacks than the default lbr call stack
|
it can recreate better call stacks than the default lbr call stack
|
||||||
output. But this approach is not full proof. There can be cases
|
output. But this approach is not foolproof. There can be cases
|
||||||
where it creates incorrect call stacks from incorrect matches.
|
where it creates incorrect call stacks from incorrect matches.
|
||||||
The known limitations include exception handing such as
|
The known limitations include exception handing such as
|
||||||
setjmp/longjmp will have calls/returns not match.
|
setjmp/longjmp will have calls/returns not match.
|
||||||
|
|
|
@ -507,7 +507,7 @@ include::itrace.txt[]
|
||||||
perf record --call-graph lbr.
|
perf record --call-graph lbr.
|
||||||
Disabled by default. In common cases with call stack overflows,
|
Disabled by default. In common cases with call stack overflows,
|
||||||
it can recreate better call stacks than the default lbr call stack
|
it can recreate better call stacks than the default lbr call stack
|
||||||
output. But this approach is not full proof. There can be cases
|
output. But this approach is not foolproof. There can be cases
|
||||||
where it creates incorrect call stacks from incorrect matches.
|
where it creates incorrect call stacks from incorrect matches.
|
||||||
The known limitations include exception handing such as
|
The known limitations include exception handing such as
|
||||||
setjmp/longjmp will have calls/returns not match.
|
setjmp/longjmp will have calls/returns not match.
|
||||||
|
|
|
@ -502,7 +502,7 @@ include::itrace.txt[]
|
||||||
perf record --call-graph lbr.
|
perf record --call-graph lbr.
|
||||||
Disabled by default. In common cases with call stack overflows,
|
Disabled by default. In common cases with call stack overflows,
|
||||||
it can recreate better call stacks than the default lbr call stack
|
it can recreate better call stacks than the default lbr call stack
|
||||||
output. But this approach is not full proof. There can be cases
|
output. But this approach is not foolproof. There can be cases
|
||||||
where it creates incorrect call stacks from incorrect matches.
|
where it creates incorrect call stacks from incorrect matches.
|
||||||
The known limitations include exception handing such as
|
The known limitations include exception handing such as
|
||||||
setjmp/longjmp will have calls/returns not match.
|
setjmp/longjmp will have calls/returns not match.
|
||||||
|
|
|
@ -334,7 +334,7 @@ use '-e e1 -e e2 -G foo,foo' or just use '-e e1 -e e2 -G foo'.
|
||||||
callgraph. The option must be used with --call-graph lbr recording.
|
callgraph. The option must be used with --call-graph lbr recording.
|
||||||
Disabled by default. In common cases with call stack overflows,
|
Disabled by default. In common cases with call stack overflows,
|
||||||
it can recreate better call stacks than the default lbr call stack
|
it can recreate better call stacks than the default lbr call stack
|
||||||
output. But this approach is not full proof. There can be cases
|
output. But this approach is not foolproof. There can be cases
|
||||||
where it creates incorrect call stacks from incorrect matches.
|
where it creates incorrect call stacks from incorrect matches.
|
||||||
The known limitations include exception handing such as
|
The known limitations include exception handing such as
|
||||||
setjmp/longjmp will have calls/returns not match.
|
setjmp/longjmp will have calls/returns not match.
|
||||||
|
|
Loading…
Reference in a new issue