From: David Ahern <dsahern@gmail.com>
To: Alexander Yarygin <yarygin@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] perf kvm stat record: print kvm specific --help output
Date: Tue, 07 Oct 2014 09:10:46 -0600 [thread overview]
Message-ID: <54340276.9070708@gmail.com> (raw)
In-Reply-To: <1412611998-8690-2-git-send-email-yarygin@linux.vnet.ibm.com>
On 10/6/14, 10:13 AM, Alexander Yarygin wrote:
> +static void print_record_help(void)
> +{
> + fprintf(stderr, "\n usage: perf kvm stat record [<options>]\n\n");
> +
> + fprintf(stderr, " -p, --pid <pid> record events on existing process id\n");
> + fprintf(stderr, " -t, --tid <tid> record events on existing thread id\n");
> + fprintf(stderr, " -r, --realtime <n> collect data with this RT SCHED_FIFO priority\n");
> + fprintf(stderr, " --no-buffering collect data without buffering\n");
> + fprintf(stderr, " -a, --all-cpus system-wide collection from all CPUs\n");
> + fprintf(stderr, " -C, --cpu <cpu> list of cpus to monitor\n");
> + fprintf(stderr, " -c, --count <n> event period to sample\n");
> + fprintf(stderr, " -o, --output <file> output file name\n");
> + fprintf(stderr, " -i, --no-inherit child tasks do not inherit counters\n");
> + fprintf(stderr, " -m, --mmap-pages <pages>\n");
> + fprintf(stderr, " number of mmap data pages\n");
> + fprintf(stderr, " -v, --verbose be more verbose (show counter open errors, etc)\n");
> + fprintf(stderr, " -q, --quiet don't print any message\n");
> + fprintf(stderr, " -D, --delay <n> ms to wait before starting measurement after program start\n");
> + fprintf(stderr, " -u, --uid <user> user to profile\n");
> + fprintf(stderr, " --per-thread use per-thread mmaps\n");
> +
> + fprintf(stderr, "\nOtherwise, it is the alias of 'perf record:'\n");
> +}
Those are all perf-record options, not perf-kvm-stat-record options.
This usage should not repeat perf-record.
David
next prev parent reply other threads:[~2014-10-07 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 16:13 [PATCH RFC] perf kvm stat record: print kvm specific --help output Alexander Yarygin
2014-10-06 16:13 ` [PATCH] " Alexander Yarygin
2014-10-07 15:10 ` David Ahern [this message]
2014-10-07 15:14 ` 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=54340276.9070708@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=yarygin@linux.vnet.ibm.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 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.