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 3/3] perf config: Allow creating empty config set for config file autogeneration
Date: Fri, 8 Sep 2017 11:36:28 -0300 [thread overview]
Message-ID: <20170908143628.GB10112@kernel.org> (raw)
In-Reply-To: <1504754336-9824-1-git-send-email-treeze.taeung@gmail.com>
Em Thu, Sep 07, 2017 at 12:18:56PM +0900, Taeung Song escreveu:
> When there isn't a config file (e.g. ~/.perfconfig)
> or it has nothing, the config set wasn't created.
> If the config set not exists, a config file can't be autogenerated.
>
> So allow creating a empty config set in the above case,
> then we can support the config file autogeneration.
Applied, and rephased a bit the cset log message.
- Arnaldo
> Before:
>
> $ rm -f ~/.perfconfig
> $ perf config --user report.children=false
>
> $ cat ~/.perfconfig
> cat: /root/.perfconfig: No such file or directory
>
> But I think it should work even if there isn't a config file.
>
> After:
>
> $ rm -f ~/.perfconfig
> $ perf config --user report.children=false
>
> $ cat ~/.perfconfig
> # this file is auto-generated.
> [report]
> children = false
>
> NOTE:
> As a result, if perf_config_set__init() is failed,
> it seems that the config set isn't freed. But it isn't a problem.
> Because the config set will be freed by perf_config_set__delete()
> at the end of cmd_config().
>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
> ---
> tools/perf/util/config.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/tools/perf/util/config.c b/tools/perf/util/config.c
> index bc75596..d2b6983 100644
> --- a/tools/perf/util/config.c
> +++ b/tools/perf/util/config.c
> @@ -700,10 +700,7 @@ struct perf_config_set *perf_config_set__new(void)
>
> if (set) {
> INIT_LIST_HEAD(&set->sections);
> - if (perf_config_set__init(set) < 0) {
> - perf_config_set__delete(set);
> - set = NULL;
> - }
> + perf_config_set__init(set);
> }
>
> return set;
> --
> 2.7.4
next prev parent reply other threads:[~2017-09-08 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 3:18 [PATCH v5 3/3] perf config: Allow creating empty config set for config file autogeneration Taeung Song
2017-09-08 14:36 ` Arnaldo Carvalho de Melo [this message]
2017-09-08 17:58 ` Taeung Song
2017-09-22 16:36 ` [tip:perf/core] " 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=20170908143628.GB10112@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