> On uniprocessor, you can type `sudo monte /boot/bzImage'
> and get to `decompressing linux' in two seconds flat. (Having
> journalling filesystems rather helps with this trick). It's
> lovely.
Hmm. That sounds a little slow to me. That is about what I get
with LinuxBIOS from when I flip the power switch, and network boot..
But that is enough enjoyment of speed.
> > The biggest issue I have had is
> > with the kernel not properly shutting down devices.
>
> Monte just disables all busmastering on the PCI devices...
That might be a useful addition, as it will probably work for most
devices. However it doesn't handle non-PCI devices. And it doesn't
handle strange devices that need a different shutdown.
With module_exit() I am quiet certain the linux driver can find the
device and set it up again, because otherwise you couldn't insert,
remove, and reinsert the code as a module.
> module_exit() routines for statically-linked drivers often
> don't exist - they're in .text.exit. I guess you can just
> move .text.exit out of the /DISCARD/ section in vmlinux.lds.
> Also, take a look at user-mode-linux's do_exitcalls()
> implementation - there's no clear reason why that shouldn't
> be mainstreamed.
I like the other suggestion of extending the Hot-plug infrastructure.
In that case I just need to figure out how to logically Hot-unplug all
the devices in the system. That may be better than a
do_exitcalls()... As it automatically gets the discrimination right.
> It would be convenient to be able to directly boot a bzImage,
> but I guess elf is workable.
Well that is directly booting vmlinux, and it doesn't lock you into
booting the linux kernel which is very important to me.
> Great work, and thanks! I look forward to 2-second SMP
> reboots.
I'll love to hear how it goes.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/