From: Cedric Le Goater <clg@fr.ibm.com>
To: Kirill Korotaev <dev@sw.ru>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-arch@vger.kernel.org,
Linux Containers <containers@lists.osdl.org>,
linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH][RFC] freezer : add the TIF_FREEZE flag to all archs
Date: Tue, 11 Dec 2007 13:31:40 +0100 [thread overview]
Message-ID: <475E832C.2010601@fr.ibm.com> (raw)
In-Reply-To: <475D6C6D.5010903@sw.ru>
Kirill Korotaev wrote:
>>> From: Cedric Le Goater <clg@fr.ibm.com>
>>
>> Sorry for the delay, I somehow managed to overlook your message.
>>
>>
>>> This patch is the first step in making the refrigerator() available
>>> to all architectures, even for those without power management.
>>>
>>> The purpose of such a change is to be able to use the refrigerator()
>>> in a new control group subsystem which will implement a control group
>>> freezer.
>>
>> Hm, sounds interesting, but ...
>>
>>
>>> If you think this is safe and not utterly stupid, I'll send the rest
>>> of the patchset exporting the refrigerator to all arches.
>>
>> ... you will need to provide some details, I think.
>>
>> I also think that it's safe to define TIF_FREEZE for all architectures, but
>> the usefulness of it will very much depend on the purpose. :-)
I'm sending the full patchset, asap
> refrigerator() can be used (and is actually used in OpenVZ containers) to freeze
> container processes for checkpointing (live migration).
> So this can be used regardless system suspend and on all archs.
Exactly !
Thanks,
C.
prev parent reply other threads:[~2007-12-11 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47594F8C.7070900@fr.ibm.com>
2007-12-05 20:27 ` [linux-pm] [PATCH][RFC] freezer : add the TIF_FREEZE flag to all archs Pavel Machek
2007-12-10 16:36 ` Rafael J. Wysocki
2007-12-10 16:42 ` Kirill Korotaev
2007-12-11 12:31 ` Cedric Le Goater [this message]
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=475E832C.2010601@fr.ibm.com \
--to=clg@fr.ibm.com \
--cc=containers@lists.osdl.org \
--cc=dev@sw.ru \
--cc=linux-arch@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;
as well as URLs for NNTP newsgroup(s).