From: Pavel Machek <pavel@ucw.cz>
To: "Li, Shaohua" <shaohua.li@intel.com>
Cc: ncunningham@linuxmail.org,
Patrick Mochel <mochel@digitalimplant.org>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: -mm swsusp: do not default to platform/firmware
Date: Thu, 29 Jul 2004 09:38:21 +0200 [thread overview]
Message-ID: <20040729073821.GA828@elf.ucw.cz> (raw)
In-Reply-To: <B44D37711ED29844BEA67908EAF36F03712639@pdsmsx401.ccr.corp.intel.com>
Hi!
> >If the thread is needed for writing the image to storage, you should
> >instead set the PF_NOFREEZE process flag when creating the thread.
> >
> You know for sleep into mem (s3) we also use
> 'freeze_processes/refrigerator', and the threads don't write image to
> storage for S3. Should the threads be set the PF_NOFREEZE? Is there any
> side effect for S3 if the threads are running?
Threads that are "NOFREEZE" should be carefull not to do anything bad
to drivers, and if it works as NOFREEZE for swsusp, it will work in
S3, too. No need to do additional work of freezing based on new state.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2004-07-29 7:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 5:19 Li, Shaohua
2004-07-29 7:38 ` Pavel Machek [this message]
2004-07-29 8:03 ` Nigel Cunningham
-- strict thread matches above, loose matches on Subject: below --
2004-07-28 22:24 Pavel Machek
2004-07-28 23:14 ` Andrew Morton
2004-07-28 23:39 ` Pavel Machek
2004-07-28 23:43 ` Pavel Machek
2004-07-29 0:30 ` Nigel Cunningham
2004-07-29 7:39 ` Pavel Machek
2004-07-29 7:52 ` Nigel Cunningham
2004-08-02 6:15 ` Patrick Mochel
2004-08-02 15:30 ` Kevin Fenzi
2004-08-03 11:28 ` Karol Kozimor
2004-08-09 19:44 ` Pavel Machek
2004-08-08 17:13 ` 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=20040729073821.GA828@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=ncunningham@linuxmail.org \
--cc=shaohua.li@intel.com \
/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®