From: Joe Perches <joe@perches.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org, Len Brown <len.brown@intel.com>,
Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] power: hibernate: Use separate messages for "Syncing filesystems"
Date: Mon, 08 Jun 2015 16:23:24 -0700 [thread overview]
Message-ID: <1433805804.2730.22.camel@perches.com> (raw)
In-Reply-To: <5609150.OAJVFt04xE@vostro.rjw.lan>
On Tue, 2015-06-09 at 01:35 +0200, Rafael J. Wysocki wrote:
> On Thursday, June 04, 2015 11:36:44 AM Joe Perches wrote:
> > Add the ability to see how long it takes to sync the filesystems
> > via the printk time mechanism.
> >
> > Start to standardize the printk "PM: doing something...done"
> > messages on two separate lines.
>
> Well, it would be good to say what problem this is attempting to fix.
>
> And while I understand the underlying concern, there is a merit in keeping
> each of these messages in one line (if everything goes well), so I'm wondering
> what about printing each of them in one go after the operation with a tail
> depending on the result? Like
>
> printk(KERN_INFO "PM: Syncing filesystems ... done\n");
>
> on success or
>
> printk(KERN_INFO "PM: Syncing filesystems ... failed\n");
>
> on failure?
Maybe.
I believe there are multi-second delays possible when
syncing the filesystems on things like usb memory sticks.
I think the dmesg line count here isn't particularly important
and there's some small value in consistently presenting timing
information via dmesg timestamps when using 2 lines.
There's also some small value in patch 6/6 and the consistent
prefixing of "PM: " on all these messages.
next prev parent reply other threads:[~2015-06-08 23:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 18:36 [PATCH 0/6] kernel: power: Neaten PM: logging Joe Perches
2015-06-04 18:36 ` [PATCH 1/6] power: hibernate: Use separate messages for "Syncing filesystems" Joe Perches
2015-06-08 23:35 ` Rafael J. Wysocki
2015-06-08 23:23 ` Joe Perches [this message]
2015-06-09 9:20 ` Pavel Machek
2015-06-04 18:36 ` [PATCH 2/6] power: process: Standardize "freezing process" messages Joe Perches
2015-06-04 18:36 ` [PATCH 3/6] power: suspend: Standardize "Syncing filesystems" messages Joe Perches
2015-06-04 18:36 ` [PATCH 4/6] power: swap: Standardize "Image <loading/saving>" messages Joe Perches
2015-06-04 18:36 ` [PATCH 5/6] power: user: Standardize "Syncing filesystems ..." message Joe Perches
2015-06-05 10:37 ` Pavel Machek
2015-06-05 15:07 ` Joe Perches
2015-06-06 13:36 ` Pavel Machek
2015-06-04 18:36 ` [PATCH 6/6] power: Use pr_fmt and pr_<level> Joe Perches
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=1433805804.2730.22.camel@perches.com \
--to=joe@perches.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.