public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wojciech Moczulski <wmoczulski@gmail.com>
To: Bernard Blackham <bernard@blackham.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Suspending and resuming a single task
Date: Mon, 19 Jun 2006 16:19:13 +0200	[thread overview]
Message-ID: <4496B261.9050005@gmail.com> (raw)
In-Reply-To: <1150690028.2207.8.camel@localhost>

Bernard Blackham napisał(a):
> On Mon, 2006-06-19 at 03:06 +0200, Wojciech Moczulski wrote:
> 
>>Matthew Garrett napisał(a):
>>
>>>http://cryopid.berlios.de/ ?
>>
>>OK, and if I want to parse the path to a file, where process state is saved,
>>to the kernel and let the kernel module restart the process? Is it possible to
>>do it this way (without building self-executable binary)?
> 
> 
> One of the earlier incarnations of CryoPID did more or less this - it
> generated an ELF file with segments as laid out in the original image,
> so that the kernel ELF loaded did all the dirty work. It still required
> an extra portion of code to be injected into the binary in order to
> restore registers, file descriptors, etc. I recall the main reason I
> switched away from it was to be able to compress the images.
> 
> If you're going to be modifying the kernel in order to resume processes,
> then implementing it as an binary format handler (fs/binfmt_*) may be
> what you're looking for.

I must say I didn't thought of it in this way. First version of my concept
assumned storing task state, restoring it later and get it running by creating
a new process by hand and rewriting necessary data.

Well, thank anyway.

Regards,
Wojciech

      reply	other threads:[~2006-06-19 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  0:43 Suspending and resuming a single task Wojciech Moczulski
2006-06-19  0:47 ` Matthew Garrett
2006-06-19  1:06   ` Wojciech Moczulski
2006-06-19  4:07     ` Bernard Blackham
2006-06-19 14:19       ` Wojciech Moczulski [this message]

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=4496B261.9050005@gmail.com \
    --to=wmoczulski@gmail.com \
    --cc=bernard@blackham.com.au \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox