[m5-dev] Cron [EMAIL PROTECTED] /z/m5/regression/do-regression quick
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic passed. * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic-dual passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing-dual passed. * build/ALPHA_FS/tests/fast/quick/80.netperf-stream/alpha/linux/twosys-tsunami-simple-atomic passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-atomic passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-timing passed. * build/SPARC_SE/tests/fast/quick/00.hello/sparc/linux/simple-atomic passed. * build/SPARC_SE/tests/fast/quick/00.hello/sparc/linux/simple-timing passed. * build/SPARC_SE/tests/fast/quick/02.insttest/sparc/linux/o3-timing passed. * build/SPARC_SE/tests/fast/quick/02.insttest/sparc/linux/simple-atomic passed. * build/SPARC_SE/tests/fast/quick/02.insttest/sparc/linux/simple-timing passed. * build/X86_SE/tests/fast/quick/00.hello/x86/linux/simple-atomic passed. See /z/m5/regression/regress-2008-04-26-03:00:01 for details. ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] big memory on a 32 bit machine
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
Re: [m5-dev] big memory on a 32 bit machine
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
