From: John Stultz <john.stultz@linaro.org>
To: Colin Cross <ccross@android.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Zoran Markovic <zoran.markovic@linaro.org>,
lkml <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Android Kernel Team <kernel-team@android.com>,
Todd Poynor <toddpoynor@google.com>, San Mehat <san@google.com>,
Benoit Goby <benoit@android.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Len Brown <len.brown@intel.com>
Subject: Re: [RFC PATCH] power: Add option to log time spent in suspend
Date: Thu, 02 May 2013 11:58:22 -0700 [thread overview]
Message-ID: <5182B74E.8060909@linaro.org> (raw)
In-Reply-To: <CAMbhsRQ4tCQtSxA-5tqydKp-xQf1bnrsq7GNw5q0gk3NdPZyaA@mail.gmail.com>
On 05/02/2013 11:29 AM, Colin Cross wrote:
> On Thu, May 2, 2013 at 5:27 AM, Pavel Machek <pavel@ucw.cz> wrote:
>>
>>> dmesg is not the solution, it's not a stable api, it would require
>>> constant parsing to make sure you didn't miss data before it fell out
>>> of the ringbuffer, and sched_clock often does not (and should not)
>>> tick during suspend, so printk times don't show the time spent
>>> suspended.
>> If timing info printed is invalid, that should be fixed.
> It's not invalid, its just not measuring the time that is useful here.
> printk is measuring something similar to (but not exactly the same
> as) CLOCK_MONOTONIC, but this is measuring something similar to
> CLOCK_BOOTTIME.
One thing I'm curious about with this patch, since we measure and keep
track of suspend time in the timekeeping core, there may be enough
justification to adding this sort of debugging info the timekeeping core
itself.
Although what is being tracked with this driver isn't just total time in
suspend, but looks like more of a logarithmic histogram of suspend
times. Is there any context you can provide as to why that particular
format was chosen (which would could be added to help improve the commit
message)?
thanks
-john
next prev parent reply other threads:[~2013-05-02 18:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 22:28 [RFC PATCH] drivers: power: Add watchdog timer to catch drivers which lockup during suspend Zoran Markovic
2013-04-30 22:28 ` [RFC PATCH] power: Add option to log time spent in suspend Zoran Markovic
2013-05-01 0:29 ` Pavel Machek
2013-05-01 3:29 ` Colin Cross
2013-05-02 12:27 ` Pavel Machek
2013-05-02 18:29 ` Colin Cross
2013-05-02 18:58 ` John Stultz [this message]
2013-05-02 19:11 ` Colin Cross
2013-04-30 23:30 ` [RFC PATCH] drivers: power: Add watchdog timer to catch drivers which lockup during suspend Greg Kroah-Hartman
2013-05-01 3:36 ` Colin Cross
2013-05-01 4:17 ` Greg Kroah-Hartman
2013-05-01 4:39 ` Colin Cross
[not found] ` <CAK7N6voYXxJKWDwSj5T9Y2fKK+Y5JqN9Wm8Qoffi9N7nRnsYhw@mail.gmail.com>
2013-05-01 5:14 ` Colin Cross
2013-05-01 0:30 ` Pavel Machek
2013-05-01 3:39 ` Colin Cross
2013-05-01 10:56 ` Pavel Machek
2013-05-01 16:10 ` Colin Cross
2013-05-01 16:24 ` Greg Kroah-Hartman
2013-05-02 12:30 ` Pavel Machek
2013-05-02 18:25 ` Colin Cross
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=5182B74E.8060909@linaro.org \
--to=john.stultz@linaro.org \
--cc=benoit@android.com \
--cc=ccross@android.com \
--cc=kernel-team@android.com \
--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=san@google.com \
--cc=toddpoynor@google.com \
--cc=zoran.markovic@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).