Ronald G. Minnich wrote:
> Well, if you can show me how, I'm willing to look. Haven't had a problem
> here yet.
Now I understood how you protect your sacred area ... seems to me that,
if __va(0x90000) or __va(0x100000) happen to be in your vmalloc'ed
area, you may corrupt the new kernel.
I find it also a bit unfortunate that your code needs to have a fairly
good idea of the memory layout of what it's loading, so even the part
in kernel/sys.c is quite architecture-specific.
> FWIW using LOBOS and ext3 I can chop my laptop reboot time from 90 seconds
> or so to 43. We'd like to see it down to 5 seconds, much time is lost on
> daemon startup and that initial mount of ext2 where it seems to like to do
> a full-surface-scan of the disk :-)
Ah, seems that you don't know the secret nocheck option yet ;-)
>From my notebook's /etc/fstab:
/dev/hda1 / ext2 noatime,nocheck 1 1
etc.
> p.s. almost got linuxbios up. I'm getting screwed by the intel NVRAM
> burner, which has rules about what it's willing to write to in nvram :-)
Cool stuff ;-)
- Werner
-- _________________________________________________________________________ / Werner Almesberger, ICA, EPFL, CH werner.almesberger@ica.epfl.ch / /_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 29 2000 - 21:00:21 EST