From: David Ahern <dsahern@gmail.com>
To: Andi Kleen <andi@firstfloor.org>, acme@kernel.org
Cc: jolsa@redhat.com, linux-kernel@vger.kernel.org,
namhyung@kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf, tools, record: Support recording running/enabled time
Date: Wed, 25 Feb 2015 09:47:27 -0700 [thread overview]
Message-ID: <54EDFC9F.8010605@gmail.com> (raw)
In-Reply-To: <1424819620-16043-1-git-send-email-andi@firstfloor.org>
On 2/24/15 4:13 PM, Andi Kleen wrote:
> --- a/tools/perf/Documentation/perf-record.txt
> +++ b/tools/perf/Documentation/perf-record.txt
> @@ -241,6 +241,9 @@ Capture machine state (registers) at interrupt, i.e., on counter overflows for
> each sample. List of captured registers depends on the architecture. This option
> is off by default.
>
> +--running::
> +Record running and enabled time for read events (:S)
> +
> SEE ALSO
> --------
> linkperf:perf-stat[1], linkperf:perf-list[1]
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index d0d02a8..4fdad06 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -839,6 +839,8 @@ struct option __record_options[] = {
> "use per-thread mmaps"),
> OPT_BOOLEAN('I', "intr-regs", &record.opts.sample_intr_regs,
> "Sample machine registers on interrupt"),
> + OPT_BOOLEAN(0, "running-time", &record.opts.running_time,
> + "Record running/enabled time of read (:S) events"),
> OPT_END()
Documentation differs from option in the record command.
David
next prev parent reply other threads:[~2015-02-25 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 23:13 [PATCH] perf, tools, record: Support recording running/enabled time Andi Kleen
2015-02-25 15:13 ` Jiri Olsa
2015-02-25 15:42 ` Arnaldo Carvalho de Melo
2015-02-25 16:47 ` David Ahern [this message]
2015-02-26 11:35 ` [tip:perf/core] perf record: Support recording running/ enabled time tip-bot for Andi Kleen
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=54EDFC9F.8010605@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@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 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.