From: Anomalous Force <anomalous_force@yahoo.com>
To: ebiederm@xmission.com
Cc: linux-kernel@vger.kernel.org
Subject: holy grail
Date: Thu, 26 Dec 2002 16:51:18 -0800 (PST) [thread overview]
Message-ID: <20021227005118.18686.qmail@web13202.mail.yahoo.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1303 bytes --]
a hot swap kernel would be something like the holy grail of kernel
hacking. it would logically go something like this:
void kexec_hot_swap()
{
void *kern = load_kernel_into_mem();
syscall_queue(ENABLE); /* queue all sys calls */
irq_queue(ENABLE); /* queue all irqs */
/* bring new kernel's state inline with current one's.
this includes all data structures, module hooks, etc.
this needs to be very fast as irqs will be pending... */
synch_kernel(kern);
kernel_start(kern); /* fire in the hole... */
}
at this point the new kernel would know it is being started as a
hot swap throught a flag or something, and dequeue the irq's
that are pending, followed by the sys calls that are waiting.
if this goes how i think it should, a user running on the system
wont even know the kernel was swapped.
what do you think? is it do-able?
=====
Main Entry: anom·a·lous
1 : inconsistent with or deviating from what is usual, normal, or expected: IRREGULAR, UNUSUAL
2 (a) : of uncertain nature or classification (b) : marked by incongruity or contradiction : PARADOXICAL
synonym see IRREGULAR
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
next reply other threads:[~2002-12-27 0:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 0:51 Anomalous Force [this message]
2002-12-27 4:03 ` holy grail 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
-- 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=20021227005118.18686.qmail@web13202.mail.yahoo.com \
--to=anomalous_force@yahoo.com \
--cc=ebiederm@xmission.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