mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Taeung Song <taeung.dev@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Taeung Song <treeze.taeung@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v2 2/4] perf config: Finally write changed configs on config file at a time
Date: Tue, 9 May 2017 07:09:58 +0900	[thread overview]
Message-ID: <025e2ea8-6b7c-a8e8-2b4f-239879948d38@gmail.com> (raw)
In-Reply-To: <20170508163728.GI7891@kernel.org>



On 05/09/2017 01:37 AM, Arnaldo Carvalho de Melo wrote:
> Em Mon, May 08, 2017 at 08:07:40PM +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 finally write changed configs at a time.
>>
>> 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 | 15 ++++++++++-----
>>  1 file changed, 10 insertions(+), 5 deletions(-)
>>
>> diff --git a/tools/perf/builtin-config.c b/tools/perf/builtin-config.c
>> index 7545966..0d38599 100644
>> --- a/tools/perf/builtin-config.c
>> +++ b/tools/perf/builtin-config.c
>> @@ -33,8 +33,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;
>> @@ -48,7 +47,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 */
>> @@ -160,6 +158,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);
>> @@ -227,10 +226,16 @@ int cmd_config(int argc, const char **argv)
>>
>>  			if (value == NULL)
>>  				ret = show_spec_config(set, var);
>> -			else
>> -				ret = set_config(set, config_filename, var, value);
>> +			else {
>> +				perf_config_set__collect(set, config_filename,
>> +							 var, value);
>> +				changed = true;
>> +			}
>>  			free(arg);
>>  		}
>> +
>> +		if (changed)
>> +			ret = set_config(set, config_filename);
>
> Ok, this improves the situation, even fixing what seems like a bug, i.e.
> that ret variable set in the if (value == NULL) case is not being
> checked, the look just goes on to completion and whatever is the last
> value left in 'ret' is what will be returned by cmd_config()...
>
> I think we should fix that bug first, making it exit the loop and
> perhaps show some error message, then do this 'call set_config()' only
> at the end', no?

I understood !
will fix the bug you mentioned first,
before this patch.

>
> I applied the first patch, the one just renesting things.
>
> - Arnaldo

Thank you !,
Taeung

>
>>  	}
>>
>>  	perf_config_set__delete(set);
>> --
>> 2.7.4

      reply	other threads:[~2017-05-08 22:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08 11:07 Taeung Song
2017-05-08 16:37 ` Arnaldo Carvalho de Melo
2017-05-08 22:09   ` Taeung Song [this message]

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=025e2ea8-6b7c-a8e8-2b4f-239879948d38@gmail.com \
    --to=taeung.dev@gmail.com \
    --cc=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --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

all inboxes | Powered by JetHome®