Hi Aleksei, Back when I was running PARSEC regularly, I was using the M5 repo changeset 5589:733318abb7b1 (our patches don't work with newer versions, so we haven't yet tried to update to the current repo head). We also used something very close to the default configuration with 64 cores, each with L1 instruction and data caches, and a unified shared L2. Many of our simulations ran to completion, and I have them summarized in this file: http://www.cs.utexas.edu/~hestness/links/linux-parsec-gcc4.3.4-status.txt. The others had either crashed or were allowed to run for 20+ days and had not completed. I've also run a few more recent changesets for various tests, and some of the benchmarks (e.g. dedup, vips) have run to completion. Unfortunately, I don't recall which versions I was using. Debugging problems such as hung simulation can be really tough, especially when the simulations run for days or weeks before getting hung. My recommendation would be to use what works to get started and if you really need a particular benchmark to finish, focus on debugging it. Good luck, Joel
On Sun, Oct 3, 2010 at 3:06 AM, Lesha Jolondz <[email protected]>wrote: > Hi Joel, > > Thank you for your answer. Currently I am trying to debug default > configuration (starting at AtomicSimpleCPU and when ROI is reached switch to > Deriv03CPU) with L2 shared cache. I tried to run PARSEC benchmarks on 3 > different versions of M5. Some benchmarks have successfully run on one > version and hanged on another. What version of M5 you use to run PARSEC and > what is your configuration? > Regards, Aleksei > On Sat, Sep 11, 2010 at 7:36 AM, Joel Hestness <[email protected]>wrote: > >> Hi Aleksei, >> I've used these benchmarks fairly extensively, and I've only experienced >> problems with hangs in very old versions of M5 when using the O3 CPU model. >> Keep in mind that some of these benchmarks can run for a *long* time, so >> rather than hanging, you might just be experiencing (perceptibly) very slow >> simulation. Can you tell us more about your configuration (cache hierarchy, >> core type)? >> Unfortunately, I don't have much experience with Ruby, but I know that >> certain cache configurations and coherence protocols work. Brad Beckmann >> might be able to give a better update there. >> Joel >> >> >> On Sun, Sep 5, 2010 at 12:27 AM, Lesha Jolondz < >> [email protected]> wrote: >> >>> Hi, >>> >>> I have a troubles running Parsec benchmarks at FS mode as it is described >>> at PARSEC v2.1 for M5(http://userweb.cs.utexas.edu/~parsec_m5/). >>> When I run the benchmarks at 4 cores configuration some of them just >>> hang, depending on timing. It is probably because of a problem at current >>> memory system - a memory request gets lost. Does anybody has encountered the >>> same problem? any solutions? patches to memory system? As I know you are >>> currently working on new memory system called ruby. When are you expecting >>> it to work stable? >>> >>> Thanks in advance, >>> Aleksei >>> >>> >>> _______________________________________________ >>> m5-users mailing list >>> [email protected] >>> http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >>> >> >> >> >> -- >> Joel Hestness >> PhD Student, Computer Architecture >> Dept. of Computer Science, University of Texas - Austin >> http://www.cs.utexas.edu/~hestness >> >> _______________________________________________ >> m5-users mailing list >> [email protected] >> http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >> > > > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users > -- Joel Hestness PhD Student, Computer Architecture Dept. of Computer Science, University of Texas - Austin http://www.cs.utexas.edu/~hestness
_______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
