Re: Booting questions ....

From: Willem Jan Withagen (wjw_at_withagen.nl)
Date: 11/05/04

  • Next message: Willem Jan Withagen: "Re: Booting questions ...."
    Date: Fri, 05 Nov 2004 00:08:08 +0100
    To: Julian Elischer <julian@elischer.org>
    
    

    Julian Elischer wrote:

    >> I'm looking for a place to sensibly insert memorytest routines....
    >>
    >> Currently I'd like to do that not in the loader, but in the kernel
    >> where memory is already setup to be one flat address space. This makes
    >> programming a lot simpler.
    >
    >
    >
    > I'd argue that it should just be a program that can be loadd by the
    > loader and executed.
    >
    > memtest86 could just be loaded and run.

    Fair argument, and something that I've been contemplating as well.

    However, this is complicated by the fact that there are several architectures
    that then need to be addressed in their native mode with all the platform quirks.
    Memtest86 is not for the faint of heart to look at. The routines are straight
    forward, but getting it there and run them is not so easy. And show obvious
    why it is rather x86 specific.
    That's why it is really a seperate entity. Getting it to boot is clumsy, you
    need to put it on a floppy or CD and (re)boot.

    The next step would be to "imitate" a kernel booting to the point where I got
    and do the memory test. This then would be the seperate module/program to
    load. And you can do:

    unload
    load memtest
    boot -m 6 /* or something like this */

    And get the first 6 tests on run your memory.

    Whether the other modules of the kernel are there or not is rather not
    essential then. After completing the tests we "reboot".

    I would need some of the kernel, but as little as possible to get to 1 working
    processor, the flat memory addressspace and at least printf working.

    The advantage of this aproach is that it is (more) architecture independant,
    unless routines are again written in ASM for speed. But that I consider a
    second stage optimisation.

    --WjW
    _______________________________________________
    freebsd-arch@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-arch
    To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"


  • Next message: Willem Jan Withagen: "Re: Booting questions ...."

    Relevant Pages

    • [UNIX] Linux Kernel do_brk() Vulnerablility (Explained)
      ... Get your security news from a reliable source. ... A critical security bug has been found in the Linux kernel 2.4.22 (and ... earlier) memory management subsystem. ... for the code working at the lowest privilege level. ...
      (Securiteam)
    • Re: Cached memory never gets released
      ... Stock linux 2.4.26 kernel. ... Due to flash bug 3M of memory gets lost due to font memory getting lost ... The output of "free" cache number steadily grows. ... longer to exhaust all of system memory with the cache. ...
      (Linux-Kernel)
    • Re: memory not released after using cdrecord/cdrdao (was: audio cd writing causes massive swap and c
      ... The kernel is most definitely not releasing the memory ... I further would have to say that the kernel isn't being ... >after cdrdao or cdrecord have used it, ... the Linux Kernel maintainers have not been very helpful with Linux ...
      (Linux-Kernel)
    • Re: prefetch data abort on WinCE kernel
      ... blocking in loader initialization function it self, ... Here i am not allocating the Dll First virtual memory address to ... PB Debugger The Kernel Debugger is waiting to connect with target. ... 3600 PID:400002 TID:410002 LoaderInit: Initialing loader ...
      (microsoft.public.windowsce.platbuilder)
    • Re: Allocating kernel memory
      ... am doing has to be in kernel space - no other option. ... I never complained about the real memory that was used but pointed out ... the features of the architecture in the best possible way. ... Oh but wait, paging is there to ...
      (comp.os.linux.development.system)