From: Yanmin Zhang <yanmin_zhang@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Liu, ShuoX" <shuox.liu@intel.com>,
"linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Greg KH <gregkh@suse.de>,
"Brown, Len" <len.brown@intel.com>,
MyungJoo Ham <myungjoo.ham@gmail.com>
Subject: Re: [PATCH v4] PM: add statistics debugfs file for suspend to ram
Date: Thu, 11 Aug 2011 09:55:33 +0800 [thread overview]
Message-ID: <1313027733.1743.110.camel@ymzhang> (raw)
In-Reply-To: <20110810214418.GC9320@atrey.karlin.mff.cuni.cz>
On Wed, 2011-08-10 at 23:44 +0200, Pavel Machek wrote:
> Hi!
>
> > If not using this patch, we have other methods to get info about
> > what device fails. One is to turn on CONFIG_PM_DEBUG, but users
> > would get too much info and testers need recompile the system.
> >
> > In addition, dynamic debug is another good tool to dump debug info.
> > But it still doesn't match our utilization scenario closely.
> > 1) user need write a user space parser to process the syslog output;
> > 2) Our testing scenario is we leave the mobile for at least hours.
> > Then, check its status. No serial console available during the
> > testing. One is because console would be suspended, and the other
> > is serial console connecting with spi or HSU devices would consume
> > power. These devices are powered off at suspend-2-ram.
>
Pavel,
Thanks for your good comments. To be honest, we did consider the weakness of
the patch before sending out. There is a tradeoff we need balance.
> 1) yes you need parser
>
> 1a) Yes, you need CONFIG_PM_DEBUG; but that's better than forcing 200
> lines of pure debugging code onto everyone
The new code lines are pretty simple and direct. We don't change any logic of PM.
CONFIG_PM_DEBUG is used mostly to print out debug info timely, not for statistics.
> 2) You can do that. Just check and parse dmesg from userland after
> each resume.
Indeed, there are many methods to do so. But if we implement it in kernel directly,
more developers could benefit from it. And any new kernel patch which touches the logic
would also maintain the consistency between main PM logic and the statistics.
>
> If dmesg provides too little/too much information, improve loglevels
> so that it is not spammed.
We got very good feedback from internal 1st-line developers and testers. They raised
the requirement and we implement it.
Thanks,
Yanmin
prev parent reply other threads:[~2011-08-11 1:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 7:28 [PATCH v4] PM: add statistics debugfs file for suspend to ram Liu, ShuoX
2011-08-10 18:00 ` [linux-pm] " Mansoor, Illyas
2011-08-10 19:45 ` Greg KH
2011-08-10 19:52 ` Mansoor, Illyas
2011-08-10 19:58 ` Greg KH
2011-08-10 20:20 ` Mansoor, Illyas
2011-08-10 20:25 ` Mansoor, Illyas
2011-08-12 7:04 ` Pavel Machek
2011-08-12 7:13 ` Rafael J. Wysocki
2011-08-10 21:07 ` Rafael J. Wysocki
2011-08-10 21:44 ` Pavel Machek
2011-08-11 1:55 ` Yanmin Zhang [this message]
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=1313027733.1743.110.camel@ymzhang \
--to=yanmin_zhang@linux.intel.com \
--cc=gregkh@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=myungjoo.ham@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=shuox.liu@intel.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