PM / sleep: trace events for suspend/resume
Adds trace events that give finer resolution into suspend/resume. These events are graphed in the timelines generated by the analyze_suspend.py script. They represent large areas of time consumed that are typical to suspend and resume. The event is triggered by calling the function "trace_suspend_resume" with three arguments: a string (the name of the event to be displayed in the timeline), an integer (case specific number, such as the power state or cpu number), and a boolean (where true is used to denote the start of the timeline event, and false to denote the end). The suspend_resume trace event reproduces the data that the machine_suspend trace event did, so the latter has been removed. Signed-off-by:Todd Brandt <todd.e.brandt@intel.com> Acked-by:
Steven Rostedt <rostedt@goodmis.org> Signed-off-by:
Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Showing
- drivers/acpi/sleep.c 3 additions, 0 deletionsdrivers/acpi/sleep.c
- drivers/base/power/main.c 16 additions, 0 deletionsdrivers/base/power/main.c
- drivers/base/syscore.c 5 additions, 0 deletionsdrivers/base/syscore.c
- include/trace/events/power.h 25 additions, 17 deletionsinclude/trace/events/power.h
- kernel/cpu.c 5 additions, 0 deletionskernel/cpu.c
- kernel/power/hibernate.c 3 additions, 0 deletionskernel/power/hibernate.c
- kernel/power/process.c 3 additions, 0 deletionskernel/power/process.c
- kernel/power/suspend.c 12 additions, 2 deletionskernel/power/suspend.c
Loading
Please register or sign in to comment