Is it too difficult to track down which piece of BIOS info you copied
contains the DRAM size, or copy the info from a machine with less RAM?
 In the long run we'll want to make it configurable, and clearly in
the real world it's OK to have a PC with < 4GB of RAM...

On Sat, Apr 26, 2008 at 3:46 PM, Gabe Black <[EMAIL PROTECTED]> wrote:
>     To pass some time just now I went to try to figure out what seems
>  like a fairly simple x86 bug on my laptop from my parent's house. It
>  didn't work because my simulation wants to use 4 gigs of memory, and my
>  laptop is 32 bit and can't fit that into m5's address space. The memory
>  needs to be that large because of some information the BIOS provides
>  which I copied from a different machine and which tells the kernel
>  that's how much memory it should expect. Anyway, it seems like this, or
>  something like it, would be an annoying limitation on the simulated
>  system which depends on the guest.
>
>     I read in a book I have about the linux virtual memory manager that
>  there's some sort of mechanism for mmapping a part of a file at a time
>  into a process, but unfortunately I don't remember the details.
>  Something like that combined with some M5 level version of paging in and
>  out of the file would get around that limitation. I imagine there being
>  a different memory object (BigPhysical or something like that) to keep
>  the complication out when it isn't needed. Anyway, what does everybody
>  think?
>
>  Gabe
>  _______________________________________________
>  m5-dev mailing list
>  m5-dev@m5sim.org
>  http://m5sim.org/mailman/listinfo/m5-dev
>
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev

Reply via email to