Re: [PATCH v2] PM: Print wall time at suspend entry and exit

2014-09-22 Thread Todd Poynor
On Sat, Sep 20, 2014 at 5:04 PM, Rafael J. Wysocki wrote: > On Friday, September 19, 2014 04:57:12 AM Amit Pundir wrote: >> From: Todd Poynor >> >> Existing timestamps in a dmesg only log suspend activities >> (e.g. filesystem syncs, freezing/unfreezing tasks etc) while the >> system has already

Re: [PATCH v2] PM: Print wall time at suspend entry and exit

2014-09-22 Thread Todd Poynor
On Sat, Sep 20, 2014 at 5:04 PM, Rafael J. Wysocki r...@rjwysocki.net wrote: On Friday, September 19, 2014 04:57:12 AM Amit Pundir wrote: From: Todd Poynor toddpoy...@google.com Existing timestamps in a dmesg only log suspend activities (e.g. filesystem syncs, freezing/unfreezing tasks etc)

Re: [PATCH v2] PM: Print wall time at suspend entry and exit

2014-09-20 Thread Rafael J. Wysocki
On Friday, September 19, 2014 04:57:12 AM Amit Pundir wrote: > From: Todd Poynor > > Existing timestamps in a dmesg only log suspend activities > (e.g. filesystem syncs, freezing/unfreezing tasks etc) while the > system has already started to enter/exit the suspend state. > > Sometimes it is

Re: [PATCH v2] PM: Print wall time at suspend entry and exit

2014-09-20 Thread Rafael J. Wysocki
On Friday, September 19, 2014 04:57:12 AM Amit Pundir wrote: From: Todd Poynor toddpoy...@google.com Existing timestamps in a dmesg only log suspend activities (e.g. filesystem syncs, freezing/unfreezing tasks etc) while the system has already started to enter/exit the suspend state.

[PATCH v2] PM: Print wall time at suspend entry and exit

2014-09-18 Thread Amit Pundir
From: Todd Poynor Existing timestamps in a dmesg only log suspend activities (e.g. filesystem syncs, freezing/unfreezing tasks etc) while the system has already started to enter/exit the suspend state. Sometimes it is handy to have suspend entry/exit overhead information while debugging suspend

[PATCH v2] PM: Print wall time at suspend entry and exit

2014-09-18 Thread Amit Pundir
From: Todd Poynor toddpoy...@google.com Existing timestamps in a dmesg only log suspend activities (e.g. filesystem syncs, freezing/unfreezing tasks etc) while the system has already started to enter/exit the suspend state. Sometimes it is handy to have suspend entry/exit overhead information