From: Helge Hafting <helgehaf@idb.hist.no>
To: "C. Slater" <cslater@wcnet.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Switching Kernels without Rebooting?
Date: Wed, 11 Jul 2001 11:10:38 +0200 [thread overview]
Message-ID: <3B4C180E.D3AE1960@idb.hist.no> (raw)
In-Reply-To: <NOEJJDACGOHCKNCOGFOMOEKECGAA.davids@webmaster.com> <001501c10980$f42035a0$fe00000a@cslater>
"C. Slater" wrote:
> I don't think that it would be possible to switch kernels when one was not
> properly set up to do it, if thats what you mean. You could only switch
> between kernels that have been compiled to support live switching.
>
Sure.
> I do see you'r point with the datastructures changeing. We would need to use
> some format that all properly setup kernels could understand,
That seems completely out of question. The structures a 2.4.7
kernel understands might be insufficient to express the setup
a future 2.6.9 kernel is using to do its stuff better. (And vice
versa, if future kernels drop a 2.4.7 feature deemed obsolete.
But what if that feature is in use when you decide to upgrade?)
You can easily deal with simple stuff like struct
rearrangement and type conversions, but what to do when whole data
structures
change completely?
Example: something changes from two linked lists representation to a
single tree or 4 hashtables. You'll have a very hard time inventing
a generic data format to deal with that kind of changes. It might
happen. Look at differences in 2.2 and 2.4 VM with the big pagecache
change in early 2.3. And the dentry cache that suddenly appeared.
And of course the rules change too, from time to time.
Many releases have a list of "active pages". what kind exactly is that?
The rules may change, what to do if the new kernel don't allow
one particular kind of page on that list, but the old running kernel
have a bunch?
This was jsut some made-up examples, I guess you'll run into a ton
of such issues. New releases aren't simply fixes and tweaks, there
are frequent design changes.
> Are you saying that swaping the kernels out altogether would be a massive
> task, or that saveing/restoring the datastructures would be a massive task.
All you need to swap kernel images is memory. Swapping structures
can't be done in a generic way, you'll need code that convert the
structures of one particular kernel release to those of a
particular other kernel. And I don't think you'll have the usual
kernel developers do that.
A "long-term uptime" distro might do this kind of work for a few
selected kernels, but I cannot imagine it happen for the regular
ones.
Helge Hafting
next prev parent reply other threads:[~2001-07-11 9:11 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NOEJJDACGOHCKNCOGFOMOEKECGAA.davids@webmaster.com>
2001-07-10 20:43 ` Switching Kernels without Rebooting? C. Slater
2001-07-11 3:50 ` FORT David
2001-07-11 9:10 ` Helge Hafting [this message]
2001-07-11 15:41 ` C. Slater
2001-07-11 18:11 ` Switching Kernels without Rebooting? [MOSIX] Carlos O'Donell Jr.
2001-07-12 10:16 ` Switching Kernels without Rebooting? 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-12 23:24 ` swsusp again [was Re: Switching Kernels without Rebooting?] Pavel Machek
2001-07-13 21:08 ` Alan Cox
2001-07-11 22:46 ` Switching Kernels without Rebooting? 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-13 1:11 tas
2001-07-13 3:45 ` Ian Stirling
-- strict thread matches above, loose matches on Subject: below --
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
2001-07-11 9:52 David Balazic
2001-07-11 10:08 ` Laramie Leavitt
2001-07-11 19:12 ` H. Peter Anvin
2001-07-11 15:19 ` C. Slater
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=3B4C180E.D3AE1960@idb.hist.no \
--to=helgehaf@idb.hist.no \
--cc=cslater@wcnet.org \
--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