| Ashwin Chaugule | f298445 | 2012-08-21 13:27:37 -0400 | [diff] [blame] | 1 | perf-script-json-export(1) |
| 2 | ==================== |
| 3 | |
| 4 | NAME |
| 5 | ---- |
| 6 | perf-script-json-export - Export trace data to JSON |
| 7 | |
| 8 | SYNOPSIS |
| 9 | -------- |
| 10 | [verse] |
| 11 | 'perf script' -g JSON:<script> |
| 12 | 'perf script' -g <script.json> |
| 13 | 'perf script' -s JSON:<script> [option]* |
| 14 | 'perf script' -s <script.json> [option]* |
| 15 | |
| 16 | DESCRIPTION |
| 17 | ----------- |
| 18 | |
| 19 | This perf script option is used to export perf script data using JSON |
| 20 | format. JSON export extesion is identified either by the 'JSON:' |
| 21 | prefix or the '.json' file extension. |
| 22 | |
| 23 | Both command forms export JSON fomatted data. The '-g'/'--gen-script' |
| 24 | option does not include actual event data. Only Definitions. '-s' |
| 25 | version includes events and definition data (by default). |
| 26 | |
| 27 | SEE ALSO |
| 28 | -------- |
| 29 | linkperf:perf-script[1] |