From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Question about process freezing
Date: Wed, 21 Nov 2007 08:46:26 +0100 [thread overview]
Message-ID: <4743E252.2010805@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0711201036340.3931-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Tue, 20 Nov 2007, Franck Bui-Huu wrote:
>> Instead of freezing every single user land processes by sending them a
>> fake signal and waiting for them to go to the refrigerator, why not
>> freezing the scheduler ?
>
> Because processes can't simply be frozen immediately. They need to
> have a chance to release any important locks or mutexes they may be
> holding.
>
You mean any locks held by a frozen process and needed by the suspend
code path ?
thanks,
Franck
next prev parent reply other threads:[~2007-11-21 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 9:11 Question about process freezing Franck Bui-Huu
2007-11-20 15:37 ` Alan Stern
2007-11-21 7:46 ` Franck Bui-Huu [this message]
2007-11-21 13:58 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2006-12-11 2:05 question " Bob YANG
2006-12-11 20:33 ` Rafael J. Wysocki
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=4743E252.2010805@gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
/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