From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Switching Kernels without Rebooting?
Date: 11 Jul 2001 12:12:35 -0700 [thread overview]
Message-ID: <9ii8f3$pc9$1@cesium.transmeta.com> (raw)
In-Reply-To: <3B4C21DA.5FFCBE2@uni-mb.si> <JKEGJJAJPOLNIFPAEDHLGEEFDFAA.laramie.leavitt@btinternet.com>
Followup to: <JKEGJJAJPOLNIFPAEDHLGEEFDFAA.laramie.leavitt@btinternet.com>
By author: "Laramie Leavitt" <laramie.leavitt@btinternet.com>
In newsgroup: linux.dev.kernel
>
> So if the Two Kernel Monte patch was combined with the
> system suspend/resume in swap patch then you add some
> transitions so that the code path does this:
>
> 1- Suspend->Monte
> 2- Monte->Load new Kernel
> 3- Load->Resume.
>
> If it was just for very similar kernels, i.e. most
> -pre and -ac kernels it would probably work fine.
> If not, then you could just do the Monte route.
>
The problem is that "freezing" the kernel state and then
reconstructing it into a form USABLE BY ANOTHER KERNEL (not even
necessarily another kernel version) is unbelievably hard; furthermore,
it imposes a severe constrains about the kind of changes you're
allowed to make during your kernel development.
It's a bad idea, folks. Give it up.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-07-11 19:13 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 9:52 Switching Kernels without Rebooting? David Balazic
2001-07-11 10:08 ` Laramie Leavitt
2001-07-11 19:12 ` H. Peter Anvin [this message]
2001-07-11 15:19 ` C. Slater
-- strict thread matches above, loose matches on Subject: below --
2001-07-13 1:11 tas
2001-07-13 3:45 ` Ian Stirling
2001-07-12 15:32 Jesse Pollard
2001-07-12 12:23 Jesse Pollard
2001-07-12 14:55 ` Ralf Baechle
2001-07-12 4:48 Frank Davis
2001-07-12 5:08 ` John Alvord
2001-07-13 9:10 ` Chuck Hemker
2001-07-12 1:03 Torrey Hoffman
2001-07-12 1:24 ` C. Slater
2001-07-12 10:07 ` Jesse Pollard
2001-07-12 12:11 ` Ian Stirling
2001-07-12 12:54 ` Jesse Pollard
2001-07-12 14:15 ` Michael H. Warfield
2001-07-12 23:17 ` Pavel Machek
2001-07-12 20:47 ` Wilfried Weissmann
[not found] <994895240.21189@whiskey.enposte.net>
2001-07-12 0:10 ` Stuart Lynne
[not found] <NOEJJDACGOHCKNCOGFOMOEKECGAA.davids@webmaster.com>
2001-07-10 20:43 ` C. Slater
2001-07-11 3:50 ` FORT David
2001-07-11 9:10 ` Helge Hafting
2001-07-11 15:41 ` C. Slater
2001-07-12 10:16 ` Helge Hafting
2001-07-11 22:12 ` Paul Jakma
2001-07-11 22:14 ` Rik van Riel
2001-07-11 22:36 ` C. Slater
2001-07-11 23:44 ` Andreas Dilger
2001-07-12 1:17 ` C. Slater
2001-07-12 15:39 ` Rik van Riel
2001-07-12 16:23 ` Albert D. Cahalan
2001-07-12 17:37 ` Mike Borrelli
2001-07-12 18:05 ` Rik van Riel
2001-07-13 10:07 ` Pau Aliagas
2001-07-12 18:48 ` Chris Friesen
2001-07-12 10:12 ` Ralf Baechle
2001-07-12 15:32 ` Rik van Riel
2001-07-11 22:36 ` David Schwartz
2001-07-12 7:23 ` Kai Henningsen
2001-07-12 10:05 ` Helge Hafting
2001-07-13 6:50 ` Kai Henningsen
2001-07-12 17:58 ` Hua Zhong
2001-07-11 22:46 ` Kip Macy
2001-07-11 23:02 ` Rik van Riel
2001-07-12 0:31 ` Jesse Pollard
2001-07-12 1:10 ` Hua Zhong
2001-07-11 23:36 ` H. Peter Anvin
2001-07-12 7:23 ` Ville Herva
2001-07-10 18:42 C. Slater
2001-07-10 18:50 ` Chris Wedgwood
2001-07-10 21:11 ` Jesper Juhl
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='9ii8f3$pc9$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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