I'm still running m5-2.0b2 with my TM extensions but have run into a problem. I am running a benchmark that takes up a very large amount of virtual memory, and eventually needs to use the swap disk in FS mode. My first question is, after looking at the code for a little bit, it looks like the COW disk is brought into main memory as it is written to, but does the disk image in memory just keep growing if needed inside M5? It seems this would be the case because after running my benchmark for a few hours, the virtual memory footprint was 11GB and continued growing. I've calculated my worst case memory footprint for the benchmark in question at needing ~3GB of memory, so running with 1024MB of RAM the swap disk will be heavily used.
Also, I'm trying to add more RAM than 1024MB to the simulation to avoid using the swap disk image, but anything over that makes Linux kernel panic. I've checked the boot log and I'm getting bizarre memory ranges like the following: Memory cluster 0 [0 - 392] Memory cluster 1 [392 - -392] Why would Linux be receiving a negative memory range? I'll keep looking, I guess it could be the console code passing bad values up to the kernel, or something not using a 64bit integer. Thanks, Geoff
_______________________________________________ m5-users mailing list m5-users@m5sim.org http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
