[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A3258B497F1C1441AD36A2E8B45FD628550DD6@scsmsx412.amr.corp.intel.com>
Date: Thu, 19 Jul 2007 14:06:01 -0700
From: "Agarwal, Lomesh" <lomesh.agarwal@...el.com>
To: <nigel@...pend2.net>, "Rafael Wysocki" <rjw@...k.pl>
Cc: <linux-kernel@...r.kernel.org>
Subject: RE: which signal is sent to freeze process?
So basically I can not install a signal handler to catch freeze signal
in the process. Right?
Is there any other way to solve the problem I am facing? After resume
some of the system calls are failing in some of my applications with
errno set as EINTR. I wanted to explore a way to not check for this
error all over the place and somehow retry failed system call. Any
ideas?
-----Original Message-----
From: Nigel Cunningham [mailto:nigel@...el.suspend2.net]
Sent: Wednesday, July 18, 2007 9:59 PM
To: Agarwal, Lomesh; Rafael Wysocki
Cc: linux-kernel@...r.kernel.org
Subject: Re: which signal is sent to freeze process?
Hi.
On Thursday 19 July 2007 14:09:56 Agarwal, Lomesh wrote:
> Can you point me to code where kernel captures process in signal
> handling and code which runs after suspend to ram is finished?
Sure.
It's in kernel/signal.c (get_signal_to_deliver) for x86 and x86_64, and
arch/<name>/kernel/signal.c for other arches. The support for other
arches is
the place x86 & x86_64 used to use - I wonder if they should be going
away
(Rafael cc'd to raise this point with him).
Regards,
Nigel
--
See http://www.tuxonice.net for Howtos, FAQs, mailing
lists, wiki and bugzilla info.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists