From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/6] Hibernation: Use common prefix in messages
Date: Tue, 27 Nov 2007 01:20:34 +0100 [thread overview]
Message-ID: <20071127002034.GC9759@elf.ucw.cz> (raw)
In-Reply-To: <200711270032.07724.rjw@sisk.pl>
Hi!
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
> kernel/power/disk.c | 38 ++++++++++++++++++++------------------
> kernel/power/snapshot.c | 24 +++++++++++++-----------
> kernel/power/swap.c | 43 +++++++++++++++++++++++--------------------
> kernel/power/swsusp.c | 10 +++++-----
> 4 files changed, 61 insertions(+), 54 deletions(-)
>
> Index: linux-2.6/kernel/power/disk.c
> ===================================================================
> --- linux-2.6.orig/kernel/power/disk.c
> +++ linux-2.6/kernel/power/disk.c
> @@ -191,7 +191,7 @@ int create_image(int platform_mode)
> */
> error = device_power_down(PMSG_FREEZE);
> if (error) {
> - printk(KERN_ERR "Some devices failed to power down, "
> + printk(KERN_ERR PREFIX "Some devices failed to power down, "
> KERN_ERR "aborting suspend\n");
This one is actually wrong. (But you did not introduce it). KERN_ERR
will be in the middle of line
> @@ -289,7 +290,7 @@ static int resume_target_kernel(void)
> local_irq_disable();
> error = device_power_down(PMSG_PRETHAW);
> if (error) {
> - printk(KERN_ERR "Some devices failed to power down, "
> + printk(KERN_ERR PREFIX "Some devices failed to power down, "
> KERN_ERR "aborting resume\n");
> goto Enable_irqs;
> }
Same here.
> @@ -482,9 +483,9 @@ int hibernate(void)
> if (error)
> goto Exit;
>
> - printk("Syncing filesystems ... ");
> + printk(KERN_INFO PREFIX "Syncing filesystems ... ");
> sys_sync();
> - printk("done.\n");
> + printk(KERN_INFO "done.\n");
No. KERN_INFO would end up in the middle of the line.
> @@ -340,7 +342,7 @@ static int save_image(struct swap_map_ha
> if (error)
> break;
> if (!(nr_pages % m))
> - printk("\b\b\b\b%3d%%", nr_pages / m);
> + printk(KERN_INFO "\b\b\b\b%3d%%", nr_pages / m);
> nr_pages++;
> }
> } while (ret > 0);
This one is wrong.
> @@ -349,7 +351,7 @@ static int save_image(struct swap_map_ha
> if (!error)
> error = err2;
> if (!error)
> - printk("\b\b\b\bdone\n");
> + printk(KERN_INFO "\b\b\b\bdone\n");
> swsusp_show_speed(&start, &stop, nr_to_write, "Wrote");
> return error;
> }
As is this. We do some pretty printing with backspaces, and <9> will
break it.
> @@ -388,8 +390,8 @@ int swsusp_write(unsigned int flags)
>
> error = swsusp_swap_check();
> if (error) {
> - printk(KERN_ERR "swsusp: Cannot find swap device, try "
> - "swapon -a.\n");
> + printk(KERN_ERR PREFIX "Cannot find swap device, try "
> + KERN_ERR "swapon -a.\n");
> return error;
Same here.
> @@ -417,9 +419,9 @@ int swsusp_write(unsigned int flags)
>
> if (!error) {
> flush_swap_writer(&handle);
> - printk("S");
> + printk(KERN_INFO PREFIX "S");
> error = mark_swapfiles(start, flags);
> - printk("|\n");
> + printk(KERN_INFO "|\n");
> }
> }
> if (error)
And here.
> @@ -526,7 +529,7 @@ static int load_image(struct swap_map_ha
> if (error)
> break;
> if (!(nr_pages % m))
> - printk("\b\b\b\b%3d%%", nr_pages / m);
> + printk(KERN_INFO "\b\b\b\b%3d%%", nr_pages / m);
> nr_pages++;
> }
> err2 = wait_on_bio_chain(&bio);
And here.
> @@ -534,7 +537,7 @@ static int load_image(struct swap_map_ha
> if (!error)
> error = err2;
> if (!error) {
> - printk("\b\b\b\bdone\n");
> + printk(KERN_INFO "\b\b\b\bdone\n");
> snapshot_write_finalize(snapshot);
> if (!snapshot_image_loaded(snapshot))
> error = -ENODATA;
...and here.
> @@ -253,10 +253,10 @@ int swsusp_shrink_memory(void)
> tmp = __shrink_memory(size - (image_size / PAGE_SIZE));
> pages += tmp;
> }
> - printk("\b%c", p[i++%4]);
> + printk(KERN_INFO "\b%c", p[i++%4]);
> } while (tmp > 0);
> do_gettimeofday(&stop);
> - printk("\bdone (%lu pages freed)\n", pages);
> + printk(KERN_INFO "\bdone (%lu pages freed)\n", pages);
> swsusp_show_speed(&start, &stop, pages, "Freed");
And here.
All in all, I do not think I like the "PREFIX" idea.
printk(PREFIX "foo");
is longer than
printk("pm: foo");
... and the extra indirection will make greping slightly harder. (I
bet I would do
grep "pm: foo" *.c
if I saw such message).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-11-27 0:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 23:25 [PATCH 0/6] Suspend and hibernation code cleanups Rafael J. Wysocki
2007-11-26 23:27 ` [PATCH 1/6] Suspend: Fix compilation warning for CONFIG_SUSPEND unset Rafael J. Wysocki
2007-11-27 0:12 ` Pavel Machek
2007-11-26 23:29 ` [PATCH 2/6] Hibernation: Move low level resume to disk.c Rafael J. Wysocki
2007-11-27 0:29 ` Pavel Machek
2007-11-27 16:06 ` Rafael J. Wysocki
2007-11-26 23:30 ` [PATCH 3/6] Suspend: Use common prefix in messages Rafael J. Wysocki
2007-11-27 0:21 ` Pavel Machek
2007-11-27 16:16 ` Rafael J. Wysocki
2007-11-26 23:31 ` [PATCH 4/6] Suspend: Fix comment in main.c Rafael J. Wysocki
2007-11-27 0:14 ` Pavel Machek
2007-11-26 23:32 ` [PATCH 5/6] Hibernation: Use common prefix in messages Rafael J. Wysocki
2007-11-27 0:20 ` Pavel Machek [this message]
2007-11-26 23:33 ` [PATCH 6/6] Hibernation: Move extern definition to header file Rafael J. Wysocki
2007-11-27 0:23 ` Pavel Machek
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=20071127002034.GC9759@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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