There's also a kernel command line option to override the bios notion of how much ram there is. Did you try that? No matter what you do, you must come up with a way to make the amount of memory configurable.
On Sat, Apr 26, 2008 at 10:00 PM, Gabe Black <[EMAIL PROTECTED]> wrote: > Well, it's not really just a value, it's a table of regions that are > reserved or not. I'm not sure exactly how the regions are identified and > I'd probably have to do a bunch of digging to figure out how to > generate one. I think I'll just wait until I get back up to UM and use > my desktop and avoid the whole problem. > > Gabe > > > > Ali Saidi wrote: > > We talked about doing precisely that several years ago. You can also > > then compress the individual pages and also hash them so that you only > > need one copy of any page that's replicated. There is a probably a > > flyspray task to do just that, but no one got around to doing it. In the > > short term though I agree with Steve, just change the value in the BIOS. > > > > Ali > > > > On Apr 26, 2008, at 5:46 PM, Gabe Black 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 > > _______________________________________________ > 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
