diff options
author | Milian Wolff <milian.wolff@kdab.com> | 2017-09-11 14:14:22 +0300 |
---|---|---|
committer | Arnaldo Carvalho de Melo <acme@redhat.com> | 2017-09-12 18:48:54 +0300 |
commit | 3192f1ed3dd3a6883d5ae31bf2ff69984ea0fd54 (patch) | |
tree | 3c404a234102966c8e0ba5a10b2b1d795353d4e9 /drivers/scsi/qla2xxx/qla_mbx.c | |
parent | cba225d6eeaf00bd8181a851fbaa7b8716337e0b (diff) | |
download | linux-3192f1ed3dd3a6883d5ae31bf2ff69984ea0fd54.tar.xz |
perf tools: Support running perf binaries with a dash in their name
Previously the part behind "perf-" was interpreted as an internal perf
command. If the suffix could not be handled, the execution was stopped.
This makes it impossible to launch perf binaries that got renamed to
have the `perf-` prefix. This is e.g. the case for appimages (e.g.
"perf-x86_64.AppImage"), but would also apply to all other scenarios
where users symlink or rename perf themselves:
Status quo with the broken behavior:
$ ln -s ./perf ./perf-custom-suffix
$ ./perf-custom-suffix list
cannot handle custom-suffix internally$
Also note the missing newline at the end of the error message.
With this patch applied, the above works properly:
$ ./perf-custom-suffix list
List of pre-defined events (to be used in -e):
...
Signed-off-by: Milian Wolff <milian.wolff@kdab.com>
Acked-by: David Ahern <dsahern@gmail.com>
Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Yao Jin <yao.jin@linux.intel.com>
Link: http://lkml.kernel.org/r/20170911111422.31903-1-milian.wolff@kdab.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Diffstat (limited to 'drivers/scsi/qla2xxx/qla_mbx.c')
0 files changed, 0 insertions, 0 deletions