public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: pavel@ucw.cz, rjw@sisk.pl, len.brown@intel.com,
	gregkh@linuxfoundation.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, shuahkhan@gmail.com
Subject: Re: [PATCH v2] power: Include additional information in pm_print_times
Date: Fri, 14 Jun 2013 13:55:01 -0700	[thread overview]
Message-ID: <1371243301.31941.61.camel@joe-AO722> (raw)
In-Reply-To: <1371242124-11452-1-git-send-email-shuah.kh@samsung.com>

On Fri, 2013-06-14 at 14:35 -0600, Shuah Khan wrote:
> Change __device_suspend() path to include driver name and the ops that
> get run for a device. This additional information helps associate the
> driver and the type of pm_ops the device uses in the suspend path very
> quickly which will aid in debugging problems in suspend and resume paths.
> Changed both start and end debug messages to include pm_ops information
> and use dev_info() instead of pr_info().
> 
> dmesg output before the change:
> 
> [  164.390032] calling  1-1+ @ 69, parent: usb1
> [  164.390035] call 1-1+ returned 0 after 0 usecs

> dmesg output after the change:
> 
> [   58.707002] usb usb1: calling type pm ops @ 57, parent: 0000:00:1d.0
> [   58.707641] usb usb1: call type pm ops returned 0 after 611 usecs

> diff --git a/drivers/base/power/main.c b/drivers/base/power/main.c
[]
> +static ktime_t initcall_debug_start(struct device *dev, char *info)
[]
> +		/* string in info has an extra space at the end */
> +		dev_info(dev, "calling %s@ %i, parent: %s\n",
> +			info, task_pid_nr(current),
>  			dev->parent ? dev_name(dev->parent) : "none");

>  static void initcall_debug_report(struct device *dev, ktime_t calltime,
[]
> -		pr_info("call %s+ returned %d after %Ld usecs\n", dev_name(dev),
> +		/* string in info has an extra space at the end */
> +		dev_info(dev, "call %sreturned %d after %llu usecs\n", info,
>  			error, (unsigned long long)ktime_to_ns(delta) >> 10);

Perhaps align the "calling and "call" and include
task_pid_nr(current)?

[   58.707002] usb usb1: calling type pm ops @ 57, parent: 0000:00:1d.0
[   58.707641] usb usb1: call type pm ops returned 0 after 611 usecs

so it's:

[   58.707002] usb usb1: enter 'type pm ops' @ 57, parent: 0000:00:1d.0
[   58.707641] usb usb1: exit  'type pm ops' @ 57, parent: 0000:00:1d.0, error: 0 (611 usecs)

or:

[   58.707002] usb usb1: enter 'type pm ops' @ 57, parent: 0000:00:1d.0
[   58.707641] usb usb1: exit  'type pm ops' @ 57, error:  0 (611 usecs)



  parent reply	other threads:[~2013-06-14 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14 20:35 [PATCH v2] power: Include additional information in pm_print_times Shuah Khan
2013-06-14 20:40 ` Greg KH
2013-06-14 20:55 ` Joe Perches [this message]
2013-06-17 15:06   ` Shuah Khan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1371243301.31941.61.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=shuah.kh@samsung.com \
    --cc=shuahkhan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox