From: Namhyung Kim <namhyung@kernel.org>
To: Feng Tang <feng.tang@intel.com>
Cc: acme@redhat.com, mingo@elte.hu, a.p.zijlstra@chello.nl,
andi@firstfloor.org, dsahern@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/7] perf scripts: Export a find_scripts() function
Date: Tue, 04 Sep 2012 10:09:56 +0900 [thread overview]
Message-ID: <87ipbuegpn.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1346660073-20279-5-git-send-email-feng.tang@intel.com> (Feng Tang's message of "Mon, 3 Sep 2012 16:14:30 +0800")
On Mon, 3 Sep 2012 16:14:30 +0800, Feng Tang wrote:
> So that other perf commands/browser has a way to dig out the available
> scripts info in system, this is a preparation for the script browser.
>
> Signed-off-by: Feng Tang <feng.tang@intel.com>
> ---
> tools/perf/builtin-script.c | 46 +++++++++++++++++++++++++++++++++++++++++++
> tools/perf/builtin.h | 1 +
> 2 files changed, 47 insertions(+), 0 deletions(-)
>
> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
> index 7ab86bb..d46056c 100644
> --- a/tools/perf/builtin-script.c
> +++ b/tools/perf/builtin-script.c
> @@ -1031,6 +1031,52 @@ static int list_available_scripts(const struct option *opt __used,
> exit(0);
> }
>
> +/*
> + * Return 0 if none is found, otherwise the actual scripts number.
> + *
> + * Currently we just return all the raw scripts name, and their full path.
> + *
> + */
> +int find_scripts(char **scripts_array, char **scripts_path_array)
> +{
> + struct dirent *script_next, *lang_next, script_dirent, lang_dirent;
> + char scripts_path[MAXPATHLEN];
> + DIR *scripts_dir, *lang_dir;
> + char lang_path[MAXPATHLEN];
> + struct script_desc *desc;
> + char first_half[BUFSIZ];
> + char *temp;
> + int i = 0;
> +
> + first_half[0] = 0;
> + desc = NULL;
> +
> + snprintf(scripts_path, MAXPATHLEN, "%s/scripts", perf_exec_path());
> +
> + scripts_dir = opendir(scripts_path);
> + if (!scripts_dir)
> + return -1;
> +
> + for_each_lang(scripts_path, scripts_dir, lang_dirent, lang_next) {
It'd be better if checking language supported - ie. by NO_LIBPERL and/or
NO_LIBPYTHON macro rather than showing all regardless. Also you might
consider when perf was built with no script language support.
Thanks,
Namhyung
> + snprintf(lang_path, MAXPATHLEN, "%s/%s", scripts_path,
> + lang_dirent.d_name);
> + lang_dir = opendir(lang_path);
> + if (!lang_dir)
> + continue;
> +
> + for_each_script(lang_path, lang_dir, script_dirent, script_next) {
> + sprintf(scripts_path_array[i], "%s/%s", lang_path,
> + script_dirent.d_name);
> + temp = strchr(script_dirent.d_name, '.');
> + snprintf(scripts_array[i], (temp - script_dirent.d_name) + 1,
> + "%s", script_dirent.d_name);
> + i++;
> + }
> + }
> +
> + return i;
> +}
> +
> static char *get_script_path(const char *script_root, const char *suffix)
> {
> struct dirent *script_next, *lang_next, script_dirent, lang_dirent;
> diff --git a/tools/perf/builtin.h b/tools/perf/builtin.h
> index b382bd5..3ea74ed 100644
> --- a/tools/perf/builtin.h
> +++ b/tools/perf/builtin.h
> @@ -36,4 +36,5 @@ extern int cmd_kvm(int argc, const char **argv, const char *prefix);
> extern int cmd_test(int argc, const char **argv, const char *prefix);
> extern int cmd_inject(int argc, const char **argv, const char *prefix);
>
> +extern int find_scripts(char **scripts_array, char **scripts_path_array);
> #endif
next prev parent reply other threads:[~2012-09-04 1:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 8:14 [PATCH 0/7] perf ui/browser: Add browser for perf script Feng Tang
2012-09-03 8:14 ` [PATCH 1/7] perf symbols: Filter samples with unresolved symbol when "--symbols" option is used Feng Tang
2012-09-03 8:14 ` [PATCH 2/7] perf scripts: Add --symbols option to handle specific symbols Feng Tang
2012-09-03 8:14 ` [PATCH 3/7] perf scripts: Add event_analyzing_sample-record/report Feng Tang
2012-09-03 8:14 ` [PATCH 4/7] perf scripts: Export a find_scripts() function Feng Tang
2012-09-04 1:09 ` Namhyung Kim [this message]
2012-09-04 1:34 ` Namhyung Kim
2012-09-03 8:14 ` [PATCH 5/7] perf ui/browser: Add a browser for perf script Feng Tang
2012-09-04 1:57 ` Namhyung Kim
2012-09-04 9:13 ` Feng Tang
2012-09-05 0:33 ` Namhyung Kim
2012-09-03 8:14 ` [PATCH 6/7] perf ui/browser: Integrate script browser into annotation browser Feng Tang
2012-09-03 8:14 ` [PATCH 7/7] perf ui/browser: Integrate script browser into main hists browser Feng Tang
2012-09-04 0:50 ` [PATCH 0/7] perf ui/browser: Add browser for perf script Namhyung Kim
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=87ipbuegpn.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.