From: Joe Perches <joe@perches.com>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: len.brown@intel.com, pavel@ucw.cz, rjw@sisk.pl,
gregkh@linuxfoundation.org, rostedt@goodmis.org,
fweisbec@gmail.com, mingo@redhat.com,
paul.gortmaker@windriver.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, shuahkhan@gmail.com
Subject: Re: [PATCH v2] power: new trace event to print device suspend and resume time
Date: Wed, 17 Jul 2013 09:08:45 -0700 [thread overview]
Message-ID: <1374077325.1949.94.camel@joe-AO722> (raw)
In-Reply-To: <1374076659-3444-1-git-send-email-shuah.kh@samsung.com>
On Wed, 2013-07-17 at 09:57 -0600, Shuah Khan wrote:
> A new trace event is added to pm events to print time it takes to suspend and
> resume a device. It generates trace message that includes device, driver,
> parent information in addition to the type of pm ops invoked as well as the
> pm event and error status from the pm ops. Example trace below:
>
> bash-2484 [001] .... 907.330148: device_pm_report_time: backlight acpi_video0 parent=0000:00:02.0 state=freeze ops=class usecs=0 err=0
>
> bash-2484 [001] .... 909.906743: device_pm_report_time: backlight acpi_video0 parent=0000:00:02.0 state=restore ops=class usecs=0 err=0
Hi again Shuah.
A few things:
> diff --git a/include/trace/events/power.h b/include/trace/events/power.h
[]
> + TP_printk("%s %s parent=%s state=%s ops=%s usecs=%lld err=%d\n",
As I wrote before, do not end a TP_printk with "\n",
All TP_printks are self-contained and are not possible
to use a thing like pr_cont so no newline is ever used.
Use:
TP_printk("%s %s parent=%s state=%s ops=%s usecs=%lld err=%d",
Given the data is in nsecs, why use usecs for the time?
I think full resolution would be better.
Why are there two spaces after "ops=class"? One would be more normal.
next prev parent reply other threads:[~2013-07-17 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 15:57 Shuah Khan
2013-07-17 16:08 ` Joe Perches [this message]
2013-07-17 16:30 ` Shuah Khan
2013-07-17 16:41 ` Joe Perches
2013-07-17 16:43 ` Joe Perches
2013-07-17 17:10 ` Shuah Khan
2013-07-17 21:53 ` Rafael J. Wysocki
2013-07-17 16:34 ` Steven Rostedt
2013-07-17 17: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=1374077325.1949.94.camel@joe-AO722 \
--to=joe@perches.com \
--cc=fweisbec@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®