From: Taeung Song <treeze.taeung@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, jolsa@redhat.com,
namhyung@kernel.org, linux-perf-users@vger.kernel.org,
Taeung Song <treeze.taeung@gmail.com>
Subject: [PATCH v2 4/4] perf tools: Add a option 'remove' to perf-config.
Date: Fri, 29 May 2015 14:42:48 +0900 [thread overview]
Message-ID: <1432878168-11278-4-git-send-email-treeze.taeung@gmail.com> (raw)
In-Reply-To: <1432878168-11278-1-git-send-email-treeze.taeung@gmail.com>
A option 'remove' is to remove specific config variables.
For the syntax examples,
# perf config -r | --remove [section.name ...]
Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
---
tools/perf/Documentation/perf-config.txt | 6 ++++++
tools/perf/builtin-config.c | 25 ++++++++++++++++++++++++-
2 files changed, 30 insertions(+), 1 deletion(-)
diff --git a/tools/perf/Documentation/perf-config.txt b/tools/perf/Documentation/perf-config.txt
index e33e481..a543e1b 100644
--- a/tools/perf/Documentation/perf-config.txt
+++ b/tools/perf/Documentation/perf-config.txt
@@ -13,6 +13,8 @@ or
'perf config' -l | --list
or
'perf config' -a | --list-all
+or
+'perf config' -r | --remove [section.name ...]
DESCRIPTION
-----------
@@ -29,6 +31,10 @@ OPTIONS
--list-all::
Show current and all possible config variables with default values.
+-r::
+--remove::
+ Remove specific config variables.
+
CONFIGURATION FILE
------------------
diff --git a/tools/perf/builtin-config.c b/tools/perf/builtin-config.c
index cf7d61d..b7afe6e 100644
--- a/tools/perf/builtin-config.c
+++ b/tools/perf/builtin-config.c
@@ -22,12 +22,14 @@ static const char * const config_usage[] = {
#define ACTION_LIST (1<<0)
#define ACTION_LIST_ALL (1<<1)
+#define ACTION_REMOVE (1<<2)
static const struct option config_options[] = {
OPT_GROUP("Action"),
OPT_BIT('l', "list", &actions, "show current config variables", ACTION_LIST),
OPT_BIT('a', "list-all", &actions,
"show current and all possible config variables with default values", ACTION_LIST_ALL),
+ OPT_BIT('r', "remove", &actions, "remove specific variables: [section.name ...]", ACTION_REMOVE),
OPT_END()
};
@@ -471,7 +473,15 @@ static int set_config(const char *section_name, const char *name, char *value)
struct config_element *element_node = NULL;
find_config(§ion_node, &element_node, section_name, name);
- if (value != NULL) {
+ if (!value) {
+ /* value == NULL means remove the variable */
+ if (section_node && element_node) {
+ if (!element_node->value)
+ free(element_node->value);
+ element_node->value = NULL;
+ } else
+ pr_err("Error: Failed to find the variable.\n");
+ } else {
value = normalize_value(section_name, name, value);
/* if there isn't existent section, add a new section */
@@ -490,6 +500,7 @@ static int set_config(const char *section_name, const char *name, char *value)
element_node->value = value;
}
}
+
return perf_configset_write_in_full();
}
@@ -633,6 +644,18 @@ int cmd_config(int argc, const char **argv, const char *prefix __maybe_unused)
else
goto out_err;
goto out;
+ case ACTION_REMOVE:
+ for (i = 0; argv[i]; i++) {
+ if (value == NULL)
+ ret = perf_configset_with_option(set_config, argv[i], NULL);
+ else {
+ pr_err("invalid key: %s\n", argv[i]);
+ return -1;
+ }
+ if (ret < 0)
+ goto out;
+ }
+ goto out;
default:
if (!has_option && argc == 0) {
ret = perf_config(show_config, NULL);
--
1.9.1
prev parent reply other threads:[~2015-05-29 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 5:42 [PATCH v2 1/4] perf tools: Add 'perf-config' command Taeung Song
2015-05-29 5:42 ` [PATCH v2 2/4] perf tools: Add functions which can get or set perf config variables Taeung Song
2015-05-29 5:42 ` [PATCH v2 3/4] perf tools: Add a option 'list-all' to perf-config Taeung Song
2015-05-29 5:42 ` 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=1432878168-11278-4-git-send-email-treeze.taeung@gmail.com \
--to=treeze.taeung@gmail.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).