thermometer.8 2.9 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192
  1. .TH THERMOMETER 8
  2. # SPDX-License-Identifier: GPL-2.0
  3. .SH NAME
  4. \fBthermometer\fP - A thermal profiling tool
  5. .SH SYNOPSIS
  6. .ft B
  7. .B thermometer
  8. .RB [ options ]
  9. .RB [ command ]
  10. .br
  11. .SH DESCRIPTION
  12. \fBthermometer \fP captures the thermal zones temperature at a
  13. specified sampling period. It is optimized to reduce as much as
  14. possible the overhead while doing the temperature acquisition in order
  15. to prevent disrupting the running application we may want to profile.
  16. This low overhead also allows a high rate sampling for the temperature
  17. which could be necessary to spot overshots and undershots.
  18. If no configuration file is specified, then all the thermal zones will
  19. be monitored at 4Hz, so every 250ms. A configuration file specifies
  20. the thermal zone names and the desired sampling period. A thermal zone
  21. name can be a regular expression to specify a group of thermal zone.
  22. The sampling of the different thermal zones will be written into
  23. separate files with the thermal zone name. It is possible to specify a
  24. postfix to identify them for example for a specific scenario. The
  25. output directory can be specified in addition.
  26. Without any parameters, \fBthermometer \fP captures all the thermal
  27. zone temperatures every 250ms and write to the current directory the
  28. captured files postfixed with the current date.
  29. If a running \fBduration\fP is specified or a \fBcommand\fP, the
  30. capture ends at the end of the duration if the command did not
  31. finished before. The \fBduration\fP can be specified alone as well as
  32. the \fBcommand\fP. If none is specified, the capture will continue
  33. indefinitively until interrupted by \fBSIGINT\fP or \fBSIGQUIT\fP.
  34. .PP
  35. .SS Options
  36. .PP
  37. The \fB-h, --help\fP option shows a short usage help
  38. .PP
  39. The \fB-o <dir>, --output <dir>\fP option defines the output directory to put the
  40. sampling files
  41. .PP
  42. The \fB-c <config>, --config <config>\fP option specifies the configuration file to use
  43. .PP
  44. The \fB-d <seconds>, --duration <seconds>\fP option specifies the duration of the capture
  45. .PP
  46. The \fB-l <loglevel>, --loglevel <loglevel>\fP option sets the loglevel [DEBUG,INFO,NOTICE,WARN,ERROR]
  47. .PP
  48. The \fB-p <string>, --postfix <string>\fP option appends \fBstring\fP at the end of the capture filenames
  49. .PP
  50. The \fB-s, --syslog\fP option sets the output to syslog, default is \fBstdout\fP
  51. .PP
  52. The \fB-w, --overwrite\fP overwrites the output files if they exist
  53. .PP
  54. .PP
  55. .SS "Exit status:"
  56. .TP
  57. 0
  58. if OK,
  59. .TP
  60. 1
  61. Error with the options specified as parameters
  62. .TP
  63. 2
  64. Error when configuring the logging facility
  65. .TP
  66. 3
  67. Error when configuring the time
  68. .TP
  69. 4
  70. Error in the initialization routine
  71. .TP
  72. 5
  73. Error during the runtime
  74. .SH Capture file format
  75. Every file contains two columns. The first one is the uptime timestamp
  76. in order to find a point in time since the system started up if there
  77. is any thermal event. The second one is the temperature in milli
  78. degree. The first line contains the label of each column.
  79. .SH AUTHOR
  80. Daniel Lezcano <daniel.lezcano@kernel.org>