On Wed, 24 Mar 2021 13:57:28 -0400
Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
> Shouldn't "trace-cmd dump" also show the clock that's stored in the file,
> or will it only show the option?
>
> I'd like to see the file as well, but all I get is:
>
> [Tracing clock]
> No tracing clock saved in the file
>
> Which isn't true. It's just not an option.
Or it is at least inconsistent:
[root@bxtest trace-cmd.git]# ./tracecmd/trace-cmd dump
Tracing meta data in file trace.dat:
[Initial format]
6 [Version]
0 [Little endian]
8 [Bytes in a long]
4096 [Page size, bytes]
[Header page, 205 bytes]
[Header event, 205 bytes]
[Ftrace format, 15 events]
[Events format, 104 systems]
[Kallsyms, 6978379 bytes]
[Trace printk, 4997 bytes]
[Saved command lines, 2015 bytes]
8 [CPUs with tracing data]
[13 options]
[Flyrecord tracing data]
[Tracing clock]
No tracing clock saved in the file
[root@bxtest trace-cmd.git]# ./tracecmd/trace-cmd dump --clock
[Tracing clock]
[tsc2nsec]
-- Steve
|