From: Joe Perches <joe@perches.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Shuah Khan <shuah.kh@samsung.com>,
pavel@ucw.cz, len.brown@intel.com, gregkh@linuxfoundation.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
shuahkhan@gmail.com
Subject: Re: [PATCHv v3] power: Include additional information in pm_print_times
Date: Sat, 22 Jun 2013 18:05:50 -0700 [thread overview]
Message-ID: <1371949550.3137.16.camel@joe-AO722> (raw)
In-Reply-To: <2732229.sfB5fHUFTc@vostro.rjw.lan>
On Sat, 2013-06-22 at 21:52 +0200, Rafael J. Wysocki wrote:
> On Friday, June 21, 2013 07:27:22 PM Joe Perches wrote:
> > On Sat, 2013-06-22 at 02:24 +0200, Rafael J. Wysocki wrote:
> > > Namely, there are tools that use these messages to create suspend/resume time
> > > charts and they will stop working after the proposed changes.
> >
> > dmesg output isn't guaranteed to be stable.
>
> So?
So even if new information was only appended to
the existing line, the script could break.
If any script needs something stable it should
depend on information available through other
sources like trace or proc or sysfs.
Tools that use dmesg should adapt to whatever gets
thrown at it and handle the output from whatever
kernel versions the script supports.
For instance, what happens to the script when
console_level is set to 1?
Requiring that no one can change a dmesg to
add or improve the content for readability
or intelligibility I think unreasonable.
next prev parent reply other threads:[~2013-06-23 1:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 19:36 Shuah Khan
2013-06-17 19:41 ` Greg KH
2013-06-17 20:24 ` Alan Stern
2013-06-18 14:54 ` Shuah Khan
2013-06-22 0:24 ` Rafael J. Wysocki
2013-06-22 0:58 ` Shuah Khan
2013-06-23 11:36 ` Rafael J. Wysocki
2013-06-23 11:34 ` Joe Perches
2013-06-23 21:59 ` Rafael J. Wysocki
2013-06-24 16:25 ` Shuah Khan
2013-06-24 16:37 ` Shuah Khan
2013-06-24 19:45 ` Rafael J. Wysocki
2013-06-24 20:38 ` Shuah Khan
2013-06-22 2:27 ` Joe Perches
2013-06-22 19:52 ` Rafael J. Wysocki
2013-06-23 1:05 ` Joe Perches [this message]
2013-06-23 9:54 ` Pavel Machek
2013-06-23 10:07 ` Rafael J. Wysocki
2013-06-23 10:03 ` Joe Perches
2013-06-23 10:22 ` Rafael J. Wysocki
2013-06-23 10:16 ` Joe Perches
2013-06-23 10:35 ` Rafael J. Wysocki
2013-06-23 10:41 ` Joe Perches
2013-06-23 11:24 ` Rafael J. Wysocki
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=1371949550.3137.16.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
all inboxes | Powered by JetHome®