From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Taeung Song <treeze.taeung@gmail.com>
Cc: linux-kernel@vger.kernel.org, taeung@kosslab.kr,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v5 2/3] perf config: Once write a config file in the end, not a repeat
Date: Fri, 8 Sep 2017 11:33:56 -0300 [thread overview]
Message-ID: <20170908143356.GA10112@kernel.org> (raw)
In-Reply-To: <1504754331-9776-1-git-send-email-treeze.taeung@gmail.com>
Em Thu, Sep 07, 2017 at 12:18:51PM +0900, Taeung Song escreveu:
> Currently set_config() can be repeatedly called for each
> input config on the below case:
>
> $ perf config kmem.default=slab report.children=false ...
>
> But it's a waste, so only once write a config file
> gathering all given config key=value pairs
Thanks, applied.
- Arnaldo
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
> ---
> tools/perf/builtin-config.c | 22 ++++++++++++++++------
> 1 file changed, 16 insertions(+), 6 deletions(-)
>
> diff --git a/tools/perf/builtin-config.c b/tools/perf/builtin-config.c
> index a1d82e3..b89417d 100644
> --- a/tools/perf/builtin-config.c
> +++ b/tools/perf/builtin-config.c
> @@ -34,8 +34,7 @@ static struct option config_options[] = {
> OPT_END()
> };
>
> -static int set_config(struct perf_config_set *set, const char *file_name,
> - const char *var, const char *value)
> +static int set_config(struct perf_config_set *set, const char *file_name)
> {
> struct perf_config_section *section = NULL;
> struct perf_config_item *item = NULL;
> @@ -49,7 +48,6 @@ static int set_config(struct perf_config_set *set, const char *file_name,
> if (!fp)
> return -1;
>
> - perf_config_set__collect(set, file_name, var, value);
> fprintf(fp, "%s\n", first_line);
>
> /* overwrite configvariables */
> @@ -161,6 +159,7 @@ int cmd_config(int argc, const char **argv)
> struct perf_config_set *set;
> char *user_config = mkpath("%s/.perfconfig", getenv("HOME"));
> const char *config_filename;
> + bool changed = false;
>
> argc = parse_options(argc, argv, config_options, config_usage,
> PARSE_OPT_STOP_AT_NON_OPTION);
> @@ -231,15 +230,26 @@ int cmd_config(int argc, const char **argv)
> goto out_err;
> }
> } else {
> - if (set_config(set, config_filename, var, value) < 0) {
> - pr_err("Failed to set '%s=%s' on %s\n",
> - var, value, config_filename);
> + if (perf_config_set__collect(set, config_filename,
> + var, value) < 0) {
> + pr_err("Failed to add '%s=%s'\n",
> + var, value);
> free(arg);
> goto out_err;
> }
> + changed = true;
> }
> free(arg);
> }
> +
> + if (!changed)
> + break;
> +
> + if (set_config(set, config_filename) < 0) {
> + pr_err("Failed to set the configs on %s\n",
> + config_filename);
> + goto out_err;
> + }
> }
>
> ret = 0;
> --
> 2.7.4
next prev parent reply other threads:[~2017-09-08 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 3:18 [PATCH v5 2/3] perf config: Once write a config file in the end, not a repeat Taeung Song
2017-09-08 14:33 ` Arnaldo Carvalho de Melo [this message]
2017-09-22 16:35 ` [tip:perf/core] perf config: Write a config file just once tip-bot for Taeung Song
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=20170908143356.GA10112@kernel.org \
--to=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=taeung@kosslab.kr \
--cc=treeze.taeung@gmail.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