public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Agarwal, Lomesh" <lomesh.agarwal@intel.com>,
	Rafael Wysocki <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: which signal is sent to freeze process?
Date: Thu, 19 Jul 2007 14:59:18 +1000	[thread overview]
Message-ID: <200707191459.20998.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <A3258B497F1C1441AD36A2E8B45FD6285508CB@scsmsx412.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 599 bytes --]

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.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-19  4:59 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
2007-07-19  4:09   ` Agarwal, Lomesh
2007-07-19  4:59     ` Nigel Cunningham [this message]
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=200707191459.20998.nigel@nigel.suspend2.net \
    --to=nigel@nigel.suspend2.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lomesh.agarwal@intel.com \
    --cc=nigel@suspend2.net \
    --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