From: Alexander Yarygin <yarygin@linux.vnet.ibm.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH 3/3] perf kvm: Print kvm specific --help output
Date: Tue, 07 Oct 2014 15:16:19 +0400 [thread overview]
Message-ID: <87sij0f7uk.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1412669432-14833-3-git-send-email-namhyung@kernel.org> (Namhyung Kim's message of "Tue, 7 Oct 2014 17:10:32 +0900")
Hello,
Namhyung Kim <namhyung@kernel.org> writes:
> The 'perf kvm stat record' tool is an alias of 'perf record' with
> predefined kvm related options. All options that passed to 'perf kvm
> stat record' are processed by the 'perf record' tool. So, 'perf kvm
> stat record --help' prints help of usage for the 'perf record'
> command. There are a few options useful for 'perf kvm stat record',
> the rest either break kvm related output or don't change it.
>
> Let's print safe for 'perf kvm stat record' options in addition to
> general 'perf record' --help output.
We probably want s/in addition to general 'perf record' --help output//
>
> With this patch, new output looks like below:
>
> $ perf kvm stat record -h
>
> usage: perf kvm stat record [<options>]
>
> -p, --pid <pid> record events on existing process id
> -t, --tid <tid> record events on existing thread id
> -r, --realtime <n> collect data with this RT SCHED_FIFO priority
> --no-buffering collect data without buffering
> -a, --all-cpus system-wide collection from all CPUs
> -C, --cpu <cpu> list of cpus to monitor
> -c, --count <n> event period to sample
> -o, --output <file> output file name
> -i, --no-inherit child tasks do not inherit counters
> -m, --mmap-pages <pages>
> number of mmap data pages
> -v, --verbose be more verbose (show counter open errors, etc)
> -q, --quiet don't print any message
> -s, --stat per thread counts
> -D, --delay <n> ms to wait before starting measurement after program start
> -u, --uid <user> user to profile
> --per-thread use per-thread mmaps
>
> $ perf kvm stat record -n sleep 1
> Error: switch `n' is not usable
>
> usage: perf kvm stat record [<options>]
>
> Cc: Alexander Yarygin <yarygin@linux.vnet.ibm.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> tools/perf/builtin-kvm.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/tools/perf/builtin-kvm.c b/tools/perf/builtin-kvm.c
> index 460a4ce9c044..c029d0fdc93e 100644
> --- a/tools/perf/builtin-kvm.c
> +++ b/tools/perf/builtin-kvm.c
> @@ -1132,6 +1132,10 @@ kvm_events_record(struct perf_kvm_stat *kvm, int argc, const char **argv)
> "-m", "1024",
> "-c", "1",
> };
> + const char * const kvm_stat_record_usage[] = {
> + "perf kvm stat record [<options>]",
> + NULL
> + };
> const char * const *events_tp;
> events_tp_size = 0;
>
> @@ -1159,6 +1163,27 @@ kvm_events_record(struct perf_kvm_stat *kvm, int argc, const char **argv)
> for (j = 1; j < (unsigned int)argc; j++, i++)
> rec_argv[i] = argv[j];
>
> + set_option_flag(record_options, 'e', "event", PARSE_OPT_HIDDEN);
> + set_option_flag(record_options, 0, "filter", PARSE_OPT_HIDDEN);
> + set_option_flag(record_options, 'R', "raw-samples", PARSE_OPT_HIDDEN);
> +
> + set_option_flag(record_options, 'F', "freq", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 0, "group", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 'g', NULL, PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 0, "call-graph", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 'd', "data", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 'T', "timestamp", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 'P', "period", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 'n', "no-samples", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 'N', "no-buildid-cache", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 'B', "no-buildid", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 'G', "cgroup", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 'b', "branch-any", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 'j', "branch-filter", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 'W', "weight", PARSE_OPT_DISABLED);
> + set_option_flag(record_options, 0, "transaction", PARSE_OPT_DISABLED);
> +
> + record_usage = kvm_stat_record_usage;
> return cmd_record(i, rec_argv, NULL);
> }
Otherwise it works for me.
Thanks!
next prev parent reply other threads:[~2014-10-07 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 8:10 [PATCH 1/3] perf tools: Add PARSE_OPT_DISABLED flag Namhyung Kim
2014-10-07 8:10 ` [PATCH 2/3] perf tools: Export usage string and option table of perf record Namhyung Kim
2014-10-07 8:10 ` [PATCH 3/3] perf kvm: Print kvm specific --help output Namhyung Kim
2014-10-07 11:16 ` Alexander Yarygin [this message]
2014-10-15 18:50 ` Arnaldo Carvalho de Melo
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=87sij0f7uk.fsf@linux.vnet.ibm.com \
--to=yarygin@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.