From: David Ahern <dsahern@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] perf kvm: introduce --list-cmds for use by scripts
Date: Thu, 12 Dec 2013 21:32:40 -0700 [thread overview]
Message-ID: <52AA8DE8.1060901@gmail.com> (raw)
In-Reply-To: <1386869211-1971-1-git-send-email-artagnon@gmail.com>
On 12/12/13, 10:26 AM, Ramkumar Ramachandra wrote:
> Introduce
>
> $ perf kvm --list-cmds
>
> to dump a raw list of commands for use by the completion script. While
> at it, refactor kvm_usage so that there's only one copy of the command
> listing.
>
> Cc: David Ahern <dsahern@gmail.com>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
> ---
> David Ahern wrote:
> > That would work -- perhaps a #define or string near
> >
> > const char * const kvm_usage[] = {
> > "perf kvm [<options>] {top|record|report|diff|buildid-list|stat}",
> > NULL
> > };
> >
> > Building kvm_usage from the string would better - only 1 place listing the
> > commands.
>
> Something like this, perhaps? It's not too pretty though: do you have
> suggestions to prettify it?
>
> tools/perf/builtin-kvm.c | 25 +++++++++++++++++++++----
> tools/perf/perf-completion.sh | 2 +-
> 2 files changed, 22 insertions(+), 5 deletions(-)
>
> diff --git a/tools/perf/builtin-kvm.c b/tools/perf/builtin-kvm.c
> index c6fa3cb..ce44a9b 100644
> --- a/tools/perf/builtin-kvm.c
> +++ b/tools/perf/builtin-kvm.c
> @@ -1672,6 +1672,7 @@ __cmd_buildid_list(const char *file_name, int argc, const char **argv)
> int cmd_kvm(int argc, const char **argv, const char *prefix __maybe_unused)
> {
> const char *file_name = NULL;
> + bool list_cmds = false;
> const struct option kvm_options[] = {
> OPT_STRING('i', "input", &file_name, "file",
> "Input file name"),
> @@ -1692,20 +1693,36 @@ int cmd_kvm(int argc, const char **argv, const char *prefix __maybe_unused)
> "file", "file saving guest os /proc/modules"),
> OPT_INCR('v', "verbose", &verbose,
> "be more verbose (show counter open errors, etc)"),
> + OPT_BOOLEAN(0, "list-cmds", &list_cmds,
> + "list commands raw for use by scripts"),
> OPT_END()
> };
>
> + const char *const commands[] = { "top", "record", "report", "diff",
> + "buildid-list", "stat", NULL };
Building it is kind of ugly looking.
Arnaldo: what about this:
#define KVM_CMDS "top record report diff buildid-list stat"
> + char kvm_usage_str[80];
> + const char *kvm_usage[] = { NULL, NULL };
>
> - const char * const kvm_usage[] = {
> - "perf kvm [<options>] {top|record|report|diff|buildid-list|stat}",
> - NULL
const char * const kvm_usage[] = {
"perf kvm [<options>] <command>, command = " KVM_CMDS,
NULL
I would even be fine with not touching kvm_usage and having the KVM_CMDS
macro right above it -- changing one causes the other to show up in a diff.
David
next prev parent reply other threads:[~2013-12-13 4:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 10:34 [PATCH 0/2] Completion for 'perf kvm' Ramkumar Ramachandra
2013-12-11 10:34 ` [PATCH 1/2] perf completion: complete " Ramkumar Ramachandra
2013-12-11 19:50 ` Arnaldo Carvalho de Melo
2013-12-11 19:56 ` David Ahern
2013-12-12 9:09 ` Ramkumar Ramachandra
2013-12-12 16:53 ` David Ahern
2013-12-12 17:26 ` [PATCH] perf kvm: introduce --list-cmds for use by scripts Ramkumar Ramachandra
2013-12-13 4:32 ` David Ahern [this message]
2013-12-16 13:16 ` Arnaldo Carvalho de Melo
2013-12-16 15:27 ` [tip:perf/core] perf completion: Complete 'perf kvm' tip-bot for Ramkumar Ramachandra
2013-12-11 10:34 ` [PATCH 2/2] perf tools: ignore files generated by " Ramkumar Ramachandra
2013-12-11 20:01 ` Arnaldo Carvalho de Melo
2013-12-12 9:05 ` [PATCH v2] " Ramkumar Ramachandra
-- strict thread matches above, loose matches on Subject: below --
2014-03-04 1:26 [PATCH] perf kvm: introduce --list-cmds for use by scripts Ramkumar Ramachandra
2014-03-05 1:00 ` David Ahern
2014-03-05 9:51 ` Jiri Olsa
2014-03-05 16:25 ` Ramkumar Ramachandra
2014-03-13 15:52 ` Ramkumar Ramachandra
2014-03-14 13:01 ` Jiri Olsa
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=52AA8DE8.1060901@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=artagnon@gmail.com \
--cc=linux-kernel@vger.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).