diff options
| author | Arnaldo Carvalho de Melo <acme@redhat.com> | 2009-02-02 20:30:40 -0200 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2009-02-03 14:03:53 +0100 |
| commit | 08a06b83ff8b2779289f733348c669f31cb65d51 (patch) | |
| tree | c8d5c13361ff9aa8e45cd660fbcad264b8310100 /crypto/algapi.c | |
| parent | 2c9b238eb325895d3312dad64e2685783575e474 (diff) | |
| download | linux-08a06b83ff8b2779289f733348c669f31cb65d51.tar.gz linux-08a06b83ff8b2779289f733348c669f31cb65d51.tar.bz2 linux-08a06b83ff8b2779289f733348c669f31cb65d51.zip | |
blkftrace: binary tracing, synthesizing old format
Impact: new feature
With this and a blkrawverify modified not to verify the sequence numbers
we can start using the userspace tools to verify that the data produced
with the ftrace plugin works as expected.
Example:
[root@f10-1 ~]# echo 1 > /sys/block/sda/sda1/trace/enable
[root@f10-1 ~]# echo bin > /d/tracing/trace_options
[root@f10-1 ~]# echo blk > /d/tracing/current_tracer
[root@f10-1 ~]# cat /d/tracing/trace_pipe > sda1.blktrace.0
^C
[root@f10-1 ~]# ./blkrawverify --noseq sda1
Verifying sda1
CPU 0
Wrote output to sda1.verify.out
[root@f10-1 ~]# cat sda1.verify.out
---------------
Verifying sda1
---------------------
Summary for cpu 0:
1349 valid + 0 invalid (100.0%) processed
[root@f10-1 ~]#
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'crypto/algapi.c')
0 files changed, 0 insertions, 0 deletions