mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Nigel Cunningham <ncunningham@crca.org.au>,
	nigel@suspend2.net, LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Fix failure to resume from initrds.
Date: Tue, 11 Sep 2007 18:27:19 +0200	[thread overview]
Message-ID: <20070911162719.GA26206@elf.ucw.cz> (raw)
In-Reply-To: <alpine.LFD.0.999.0709110736440.16478@woody.linux-foundation.org>

Hi!

> > > Anyway, yes, init is freezable, but should it be?
> > > 
> > > I mean, shouldn't we rather add PF_NOFREEZE to kernel_init()?
> > 
> > Argh, no.  PF_NOFREEZE is inherited by the children.
> 
> Umm. All of this is __init code - why is freezability even an issue? We 
> shouldn't be suspending at this point anyway afaik..

We want to do resume sometime around here, and resume wants to run
with userspace frozen, as does suspend.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-09-11 16:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11  3:54 Nigel Cunningham
2007-09-11 11:04 ` Rafael J. Wysocki
2007-09-11 11:27   ` Nigel Cunningham
2007-09-11 11:55     ` Rafael J. Wysocki
2007-09-11 13:01       ` Nigel Cunningham
2007-09-11 13:12       ` Rafael J. Wysocki
2007-09-11 13:23         ` Rafael J. Wysocki
2007-09-11 13:41           ` Nigel Cunningham
2007-09-11 19:25             ` Rafael J. Wysocki
2007-09-11 14:39           ` Linus Torvalds
2007-09-11 16:27             ` Pavel Machek [this message]
2007-09-14 12:22 Rafael J. Wysocki
2007-09-14 12:20 ` 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=20070911162719.GA26206@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@crca.org.au \
    --cc=nigel@suspend2.net \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    /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®