From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Nigel Cunningham <ncunningham@linuxmail.org>
Subject: Re: [PATCH 1/4] swsusp: Untangle thaw_processes
Date: Sun, 19 Nov 2006 03:04:45 +0100 [thread overview]
Message-ID: <20061119020445.GB15873@elf.ucw.cz> (raw)
In-Reply-To: <200611182347.05656.rjw@sisk.pl>
Hi!
> Move the loop from thaw_processes() to a separate function and call it
> independently for kernel threads and user space processes so that the order
> of thawing tasks is clearly visible.
>
> Drop thaw_kernel_threads() which is never used.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
> include/linux/freezer.h | 6 -----
> kernel/power/process.c | 55 +++++++++++++++++++++++++++---------------------
> 2 files changed, 33 insertions(+), 28 deletions(-)
>
> Index: linux-2.6.19-rc5-mm2/include/linux/freezer.h
> ===================================================================
> --- linux-2.6.19-rc5-mm2.orig/include/linux/freezer.h
> +++ linux-2.6.19-rc5-mm2/include/linux/freezer.h
> @@ -1,8 +1,5 @@
> /* Freezer declarations */
>
> -#define FREEZER_KERNEL_THREADS 0
> -#define FREEZER_ALL_THREADS 1
> -
> #ifdef CONFIG_PM
> /*
> * Check if a process has been frozen
> @@ -60,8 +57,7 @@ static inline void frozen_process(struct
>
> extern void refrigerator(void);
> extern int freeze_processes(void);
> -#define thaw_processes() do { thaw_some_processes(FREEZER_ALL_THREADS); } while(0)
> -#define thaw_kernel_threads() do { thaw_some_processes(FREEZER_KERNEL_THREADS); } while(0)
> +extern void thaw_processes(void);
>
> static inline int try_to_freeze(void)
> {
> Index: linux-2.6.19-rc5-mm2/kernel/power/process.c
> ===================================================================
> --- linux-2.6.19-rc5-mm2.orig/kernel/power/process.c
> +++ linux-2.6.19-rc5-mm2/kernel/power/process.c
> @@ -20,6 +20,8 @@
> */
> #define TIMEOUT (20 * HZ)
>
> +#define FREEZER_KERNEL_THREADS 0
> +#define FREEZER_USER_SPACE 1
The variable is named "is_user_space"... so maybe the defines are not
strictly needed?
> + do_each_thread(g, p) {
> + if (!freezeable(p))
> + continue;
>
> + if (is_user_space(p)) {
> + if (!thaw_user_space)
> + continue;
> + } else {
> + if (thaw_user_space)
> + continue;
> + }
if (is_user_space(p) != thaw_user_space)
continue;
?
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:[~2006-11-19 2:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 22:35 [PATCH 0/4] swsusp cleanups Rafael J. Wysocki
2006-11-18 22:47 ` [PATCH 1/4] swsusp: Untangle thaw_processes Rafael J. Wysocki
2006-11-18 23:03 ` Nigel Cunningham
2006-11-19 2:04 ` Pavel Machek [this message]
2006-11-19 12:01 ` Rafael J. Wysocki
2006-11-19 21:16 ` Pavel Machek
2006-11-18 22:47 ` [PATCH 2/4] swsusp: Untangle freeze_processes Rafael J. Wysocki
2006-11-19 2:09 ` Pavel Machek
2006-11-19 12:05 ` Rafael J. Wysocki
2006-11-19 21:17 ` Pavel Machek
2006-11-18 22:48 ` [PATCH 3/4] swsusp: Fix coding style in suspend.c Rafael J. Wysocki
2006-11-19 2:05 ` Pavel Machek
2006-11-18 22:51 ` [PATCH 4/4] swsusp: Fix labels Rafael J. Wysocki
2006-11-18 23:06 ` Nigel Cunningham
2006-11-18 23:25 ` Rafael J. Wysocki
2006-11-22 22:32 ` Randy Dunlap
2006-11-22 22:50 ` Rafael J. Wysocki
2006-11-19 1:46 ` 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=20061119020445.GB15873@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.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
all inboxes | Powered by JetHome®