perf record: Fix --switch-output documentation and comment
There's no --signal-trigger option, also adding the code comment into record man page. Signed-off-by: Jiri Olsa <jolsa@kernel.org> Tested-by: Wang Nan <wangnan0@huawei.com> Cc: David Ahern <dsahern@gmail.com> Cc: Namhyung Kim <namhyung@kernel.org> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Link: http://lkml.kernel.org/r/1483431600-19887-4-git-send-email-jolsa@kernel.org Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
This commit is contained in:
parent
efd2130711
commit
60437ac02f
|
@ -430,6 +430,10 @@ that gets then processed, possibly via a perf script, to decide if that
|
||||||
particular perf.data snapshot should be kept or not.
|
particular perf.data snapshot should be kept or not.
|
||||||
|
|
||||||
Implies --timestamp-filename, --no-buildid and --no-buildid-cache.
|
Implies --timestamp-filename, --no-buildid and --no-buildid-cache.
|
||||||
|
The reason for the latter two is to reduce the data file switching
|
||||||
|
overhead. You can still switch them on with:
|
||||||
|
|
||||||
|
--switch-output --no-no-buildid --no-no-buildid-cache
|
||||||
|
|
||||||
--dry-run::
|
--dry-run::
|
||||||
Parse options then exit. --dry-run can be used to detect errors in cmdline
|
Parse options then exit. --dry-run can be used to detect errors in cmdline
|
||||||
|
|
|
@ -1636,7 +1636,7 @@ int cmd_record(int argc, const char **argv, const char *prefix __maybe_unused)
|
||||||
* overhead. Still generate buildid if they are required
|
* overhead. Still generate buildid if they are required
|
||||||
* explicitly using
|
* explicitly using
|
||||||
*
|
*
|
||||||
* perf record --signal-trigger --no-no-buildid \
|
* perf record --switch-output --no-no-buildid \
|
||||||
* --no-no-buildid-cache
|
* --no-no-buildid-cache
|
||||||
*
|
*
|
||||||
* Following code equals to:
|
* Following code equals to:
|
||||||
|
|
Loading…
Reference in a new issue