From: Namhyung Kim <namhyung@kernel.org>
To: Taeung Song <treeze.taeung@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
<linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [RFC][PATCH v9 0/2] Infrastructure code for perf-config
Date: Thu, 21 Apr 2016 10:27:16 +0900 [thread overview]
Message-ID: <20160421012716.GA4475@sejong> (raw)
In-Reply-To: <1461174157-7323-1-git-send-email-treeze.taeung@gmail.com>
On Thu, Apr 21, 2016 at 02:42:35AM +0900, Taeung Song wrote:
> Hi,
>
> We can use the config files (i.e user wide ~/.perfconfig
> and system wide $(sysconfdir)/perfconfig)
> to configure perf tools. perf-config help user
> manage the config files, not manually look into or edit them.
>
> Introduce new infrastructure code for config
> management features of perf-config subcommand.
>
> This pathset contains basic code for various purposes of configuration management
> showing current configs, in the near future,
> showing all configs with default value,
> getting current configs from the config files
> or writing configs that user type on the config files, etc.
>
> IMHO, I think this infrastructure code is needed
> to add new funcationalities for config management of perf-config.
>
> If anyone reviews this, I'd appreciate it.
For both patches,
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
>
> v9:
> - don't use the arbitrary maximum 'MAX_CONFIGS' (Arnaldo, Namhyung)
> - change two-dimensinal arrays 'default_config_items' to array of pointers (Namhyung)
> - remove needless 'enum perf_config_secion_idx'
> - add sections 'intel-pt','convert' and their items
> - modify perf_config_set__init() in accordance with new default config sections and items
> - (applied two previous patches 860b8d4 and 20105ca from this patchset)
>
> v8:
> - rebased onto the current acme/perf/core
>
> v7:
> - rename 'is_custom' to 'is_allocated' to be proper (Masami)
> - fix the code about free() or zfree() in perf_config_*__delete() (Masami)
> - check set == NULL or not in show_config() (Masami)
>
> v6:
> - don't use goto in add_config_item() (Masami)
>
> v5:
> - departmentalize perf_config_set__delete() (Arnaldo)
> - remove confusing find_config() (Arnaldo)
> - use pr_debug() instead of pr_err() (Arnaldo)
> - use zfree() instead of free() (Arnaldo)
> - more compact in perf_config_set__new() (Arnaldo)
> - rename variables 'perf_configs', 'config_items', etc. (Arnaldo)
>
> v4:
> - fill perf_config_set__delete() in collect_config() for state of error
> - fill the code setting is_custom value in add_config_item() (Namhyung)
>
> v3:
> - use the section list that contains configs each section
> instead of the single config list (Namhyung)
> - exclude a patch for '--list-all' option from this patchset
>
> v2:
> - remove perf_config_kind (user, system or both config files)
> and needless at this time, etc. (Namhyung)
> - separate this patch as several patches (Namhyung)
> - fix typing errors, etc.
>
> Taeung Song (2):
> perf config: Prepare all default configs
> perf config: Initialize perf_config_set with all default configs
>
> tools/perf/builtin-config.c | 11 ++-
> tools/perf/util/config.c | 187 ++++++++++++++++++++++++++++++++++++++++++--
> tools/perf/util/config.h | 51 +++++++++++-
> 3 files changed, 238 insertions(+), 11 deletions(-)
>
> --
> 2.5.0
>
next prev parent reply other threads:[~2016-04-21 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 17:42 [RFC][PATCH v9 0/2] Infrastructure code for perf-config Taeung Song
2016-04-20 17:42 ` [PATCH v9 1/2] perf config: Prepare all default configs Taeung Song
2016-04-20 17:42 ` [PATCH v9 2/2] perf config: Initialize perf_config_set with " Taeung Song
2016-04-21 1:27 ` Namhyung Kim [this message]
2016-04-21 1:35 ` [RFC][PATCH v9 0/2] Infrastructure code for perf-config 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=20160421012716.GA4475@sejong \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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