From: Pavel Machek <pavel@ucw.cz>
To: Anomalous Force <anomalous_force@yahoo.com>
Cc: wa@almesberger.net, ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: holy grail
Date: Fri, 27 Dec 2002 14:24:20 +0100 [thread overview]
Message-ID: <20021227132419.GA404@elf.ucw.cz> (raw)
In-Reply-To: <20021227072142.26177.qmail@web13208.mail.yahoo.com>
Hi!
> > Your best bet would be to use a system that already implements some
> > form of checkpointing or process migration, and use this to
> > preserve user space state across kexec reboots. openMosix may be
>
> [snip]
>
> preserving user state would not be so much the problem as would
> the various internal kernel data structures (vm stuff, dcache, etc.)
Actually, you want to kill vm structures, dcache etc. You only want
userspace-visible state to be carried forward to minimize possibility
of bringing bugs to new kernel.
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next prev parent reply other threads:[~2002-12-27 13:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 0:51 holy grail Anomalous Force
2002-12-27 4:03 ` Werner Almesberger
2002-12-27 7:21 ` Anomalous Force
2002-12-27 7:37 ` Ingo Oeser
2002-12-27 11:30 ` Werner Almesberger
2002-12-28 16:35 ` Anomalous Force
2002-12-28 20:43 ` Rik van Riel
2002-12-29 15:56 ` Anomalous Force
2002-12-29 16:44 ` John Bradford
2002-12-30 1:05 ` Alan Cox
2002-12-30 1:32 ` Werner Almesberger
2002-12-30 2:45 ` Jeff Dike
2002-12-30 3:55 ` David Lang
2002-12-30 4:39 ` Anomalous Force
2002-12-30 17:57 ` Eric W. Biederman
2002-12-30 13:30 ` Alan Cox
2002-12-29 23:53 ` Werner Almesberger
2002-12-27 13:24 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-30 5:00 Anomalous Force
2002-12-30 6:46 ` Ed Sweetman
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=20021227132419.GA404@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=anomalous_force@yahoo.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wa@almesberger.net \
/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