From: David Ahern <dsahern@gmail.com>
To: Milian Wolff <milian.wolff@kdab.com>, acme@kernel.org
Cc: Linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Yao Jin <yao.jin@linux.intel.com>
Subject: Re: [PATCH] perf: support running perf binaries with a dash in their name
Date: Mon, 11 Sep 2017 07:08:18 -0700 [thread overview]
Message-ID: <b7c2b440-f781-19ae-ebc7-7fba93bb4618@gmail.com> (raw)
In-Reply-To: <20170911111422.31903-1-milian.wolff@kdab.com>
On 9/11/17 4:14 AM, Milian Wolff wrote:
> 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:
>
...
> ~~~~~
> $ ./perf-custom-suffix list
>
> List of pre-defined events (to be used in -e):
> ...
> ~~~~~
>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: David Ahern <dsahern@gmail.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Yao Jin <yao.jin@linux.intel.com>
> Signed-off-by: Milian Wolff <milian.wolff@kdab.com>
> ---
> tools/perf/perf.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/perf.c b/tools/perf/perf.c
> index e0279babe0c0..7a3a39014446 100644
> --- a/tools/perf/perf.c
> +++ b/tools/perf/perf.c
> @@ -467,15 +467,19 @@ int main(int argc, const char **argv)
> * - cannot execute it externally (since it would just do
> * the same thing over again)
> *
> - * So we just directly call the internal command handler, and
> - * die if that one cannot handle it.
> + * So we just directly call the internal command handler. If that one
> + * fails to handle this, then maybe we just run a renamed perf binary
> + * that contains a dash in its name. To handle this scenario, we just
> + * fall through and ignore the "xxxx" part of the command string.
> */
> if (strstarts(cmd, "perf-")) {
> cmd += 5;
> argv[0] = cmd;
> handle_internal_command(argc, argv);
> - fprintf(stderr, "cannot handle %s internally", cmd);
> - goto out;
> + // if the command is handled, the above function does not return
> + // undo changes and fall through in such a case
Those should be /* */ not //
> + cmd -= 5;
> + argv[0] = cmd;
> }
> if (strstarts(cmd, "trace")) {
> #ifdef HAVE_LIBAUDIT_SUPPORT
>
other than that LGTM and long over due.
Acked-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2017-09-11 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 11:14 Milian Wolff
2017-09-11 14:08 ` David Ahern [this message]
2017-09-11 14:33 ` Arnaldo Carvalho de Melo
2017-09-11 15:16 ` Milian Wolff
2017-09-11 15:38 ` Arnaldo Carvalho de Melo
2017-09-13 7:46 ` [tip:perf/urgent] perf tools: Support " tip-bot for Milian Wolff
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=b7c2b440-f781-19ae-ebc7-7fba93bb4618@gmail.com \
--to=dsahern@gmail.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.com \
--cc=namhyung@kernel.org \
--cc=yao.jin@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®