mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 2/4] swsusp: Untangle freeze_processes
Date: Sun, 19 Nov 2006 03:09:26 +0100	[thread overview]
Message-ID: <20061119020926.GD15873@elf.ucw.cz> (raw)
In-Reply-To: <200611182347.16692.rjw@sisk.pl>

Hi!

> Move the loop from freeze_processes() to a separate function and call it
> independently for user space processes and kernel threads so that the order of
> freezing tasks is clearly visible.
> 
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
>  kernel/power/process.c |   88 ++++++++++++++++++++++++++++++++-----------------
>  1 file changed, 58 insertions(+), 30 deletions(-)
>

>  		do_each_thread(g, p) {
> +			if (is_user_space(p)) {
> +				if(!freeze_user_space)
> +					continue;
> +			} else {
> +				if(freeze_user_space)
> +					continue;
> +			}

Needs space between if and (, but lets use if (is_user_space() !=
freeze_user_space) trick here, too. 

> +/**
> + *	freeze_processes - tell processes to enter the refrigerator
> + *
> + *	Returns 0 on success, or the number of processes that didn't freeze,
> + *	although they were told to.
> + */

Above you point out to the broken calling convention. Perhaps this is
great time to fix it, too? Hmm, or maybe not. Patch looks good,
otherwise.

							Pavel
> +int freeze_processes(void)
> +{
> +	unsigned int nr_unfrozen;
> +
> +	printk("Stopping tasks ... ");
> +	nr_unfrozen = try_to_freeze_tasks(FREEZER_USER_SPACE);
> +	if (nr_unfrozen)
> +		return nr_unfrozen;
> +
> +	sys_sync();
> +	nr_unfrozen = try_to_freeze_tasks(FREEZER_KERNEL_THREADS);
> +	if (nr_unfrozen)
> +		return nr_unfrozen;
> +
>  	printk("done.\n");
>  	BUG_ON(in_atomic());
>  	return 0;

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-11-19  2:09 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
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 [this message]
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=20061119020926.GD15873@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

Powered by JetHome