Re: [PATCH] power: print function name of callbacks

2015-10-04 Thread Pavel Machek
On Tue 2015-09-22 10:26:37, Douglas Anderson wrote: > The printouts writen to the logs by suspend can be a bit opaque: it can > be hard to track them down to the actual function called. You might > see: It seems simple enough. Acked-by: Pavel Machek > +static ktime_t initcall_debug_start(struc

Re: [PATCH] power: print function name of callbacks

2015-09-22 Thread Doug Anderson
Hi, On Tue, Sep 22, 2015 at 10:33 AM, Brown, Len wrote: > have you used analyze_suspend? > It used to parse this output, but that was abandoned > when it cut over to using ftrace directly. > > https://01.org/suspendresume Ah, good to know about. In my case this output is enabled on shipping dev

RE: [PATCH] power: print function name of callbacks

2015-09-22 Thread Brown, Len
2015 1:27 PM > To: r...@rjwysocki.net > Cc: Dmitry Torokhov; Douglas Anderson; pa...@ucw.cz; Brown, Len; > gre...@linuxfoundation.org; linux...@vger.kernel.org; linux- > ker...@vger.kernel.org > Subject: [PATCH] power: print function name of callbacks > > The printouts writen t

[PATCH] power: print function name of callbacks

2015-09-22 Thread Douglas Anderson
The printouts writen to the logs by suspend can be a bit opaque: it can be hard to track them down to the actual function called. You might see: calling rfkill1+ @ 19473, parent: phy0 call rfkill1+ returned 0 after 1 usecs calling phy0+ @ 19473, parent: mmc2:0001:1 call phy0+ returned 0