linux-kernel - Re: [PATCH] perf, tools, record: Support recording running/enabled time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Feb 2015 09:47:27 -0700
From:	David Ahern <dsahern@...il.com>
To:	Andi Kleen <andi@...stfloor.org>, acme@...nel.org
CC:	jolsa@...hat.com, linux-kernel@...r.kernel.org,
	namhyung@...nel.org, Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH] perf, tools, record: Support recording running/enabled
 time

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/