From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Agarwal, Lomesh" <lomesh.agarwal@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: which signal is sent to freeze process?
Date: Thu, 19 Jul 2007 12:18:32 +1000 [thread overview]
Message-ID: <200707191218.32730.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <A3258B497F1C1441AD36A2E8B45FD6285507A5@scsmsx412.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
Hi.
On Thursday 19 July 2007 09:42:02 Agarwal, Lomesh wrote:
> My understanding is that Linux kernel sends a signal to freeze processes
> during suspend2ram operation. Which signal is used to achieve this?
> The problem I am facing is that some of the system calls are failing
> with EINTR errno during suspend operation and I want to install a signal
> handler for freeze signal with SA_RESTART flag. That should make the
> kernel to retry the system calls. Right?
No signal is sent. We tell affected processes that they have a signal pending,
and capture them in the signal handling code while the suspend to ram is
occuring. After the suspend to ram is finished, we recalculate whether they
have a signal pending, and let them continue.
Not being a guru on signal handling itself, I won't try to answer the question
itself :\.
Regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-19 2:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 23:42 which signal is sent to freeze process? Agarwal, Lomesh
2007-07-19 2:18 ` Nigel Cunningham [this message]
2007-07-19 4:09 ` Agarwal, Lomesh
2007-07-19 4:59 ` Nigel Cunningham
2007-07-19 21:06 ` Agarwal, Lomesh
2007-07-19 22:02 ` Rafael J. Wysocki
2007-07-19 22:19 ` Nigel Cunningham
2007-07-19 23:22 ` Agarwal, Lomesh
2007-07-20 11:24 ` Rafael J. Wysocki
2007-07-20 18:07 ` Agarwal, Lomesh
2007-07-20 22:10 ` Rafael J. Wysocki
2007-07-23 18:38 ` Agarwal, Lomesh
2007-07-23 19:25 ` Rafael J. Wysocki
2007-07-23 19:31 ` Agarwal, Lomesh
2007-07-24 16:54 ` Pavel Machek
2007-07-23 20:57 ` Agarwal, Lomesh
2007-07-23 21:50 ` Rafael J. Wysocki
2007-07-23 22:18 ` Agarwal, Lomesh
2007-07-24 9:44 ` Rafael J. Wysocki
2007-07-19 22:02 ` Rafael J. Wysocki
2007-07-25 13:41 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2007-07-23 19:52 Manfred Spraul
2007-07-23 20:11 ` Rafael J. Wysocki
2007-07-23 20:09 ` Manfred Spraul
2007-07-24 18:48 ` Manfred Spraul
2007-07-25 19:19 ` Rafael J. Wysocki
2007-07-26 21:12 ` Agarwal, Lomesh
2007-07-31 7:55 ` 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=200707191218.32730.nigel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lomesh.agarwal@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