All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirill Korotaev <dev-3ImXcnM4P+0@public.gmane.org>
To: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
Cc: linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	linux-pm-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH][RFC] freezer : add the TIF_FREEZE flag to all archs
Date: Mon, 10 Dec 2007 19:42:21 +0300	[thread overview]
Message-ID: <475D6C6D.5010903@sw.ru> (raw)
In-Reply-To: <200712101736.29676.rjw-KKrjLPT3xs0@public.gmane.org>

>>From: Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
> 
> 
> 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. :-)

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.

Thanks,
Kirill

WARNING: multiple messages have this Message-ID (diff)
From: Kirill Korotaev <dev@sw.ru>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Cedric Le Goater <clg@fr.ibm.com>,
	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: Mon, 10 Dec 2007 19:42:21 +0300	[thread overview]
Message-ID: <475D6C6D.5010903@sw.ru> (raw)
In-Reply-To: <200712101736.29676.rjw@sisk.pl>

>>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. :-)

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.

Thanks,
Kirill

  parent reply	other threads:[~2007-12-10 16:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 13:50 [PATCH][RFC] freezer : add the TIF_FREEZE flag to all archs Cedric Le Goater
2007-12-05 20:27 ` Pavel Machek
2007-12-05 20:27   ` [linux-pm] " Pavel Machek
     [not found] ` <47594F8C.7070900-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-12-10 16:36   ` Rafael J. Wysocki
2007-12-10 16:36     ` Rafael J. Wysocki
2007-12-10 16:42     ` Kirill Korotaev
     [not found]     ` <200712101736.29676.rjw-KKrjLPT3xs0@public.gmane.org>
2007-12-10 16:42       ` Kirill Korotaev [this message]
2007-12-10 16:42         ` Kirill Korotaev
2007-12-11 12:31         ` Cedric Le Goater
2007-12-11 12:31           ` Cedric Le Goater
2007-12-10 16:36 ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2007-12-07 13:50 Cedric Le Goater

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=475D6C6D.5010903@sw.ru \
    --to=dev-3imxcnm4p+0@public.gmane.org \
    --cc=clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-pm-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=rjw-KKrjLPT3xs0@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.