Re: [m5-dev] [m5-users] 01.hello-2T-smt on SPARC

2009-07-13 Thread Korey Sewell
Hi, well if you are interested in doing a some debugging you can start to uncover the problem. So that probably would signal this conversation go to the m5-dev list instead of m5-users (I think at least). If I were you, these would be my steps to figure out the problem. (1) Run a Sparc Hello World

Re: [m5-dev] Gem5 configuration

2009-07-13 Thread Derek Hower
I believe there are only a few (maybe one?) case(s) where the Ruby initialization dependencies are pretty ugly. The one I know about is a dependency between the Ruby network and the topology class. Given the limited scope of the problem, I think Steve's null init function should suffice. -Derek

Re: [m5-dev] Gem5 configuration

2009-07-13 Thread Steve Reinhardt
There's no real control over ordering... I believe init() is called on objects in the same order that they were constructed, but you don't have a lot of control over the construction order (short of the fact that if B is a parameter to A then B will be constructed first) and it's probably best not

[m5-dev] wiki updated

2009-07-13 Thread Ali Saidi
I just updated the wiki software to the latest version. If anyone notices some problems please let me know. Thanks, Ali ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev

Re: [m5-dev] Gem5 configuration

2009-07-13 Thread Somayeh Sardashti
Hi, Does M5 keep any order when calling init() of different objects? In Ruby, because of dependencies among some objects (like topology and network), the order of calling init() is important and handled in constructor of System (the main module). How can I keep this kind of ordering in M5? So

[m5-dev] changeset in m5: regression: updated memtest-ruby stats

2009-07-13 Thread Derek Hower
changeset 61f8eb04e96d in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=61f8eb04e96d description: regression: updated memtest-ruby stats This also includes a change to the default Ruby random seed, which was previously set using the wall clock. It is now

[m5-dev] changeset in m5: merge

2009-07-13 Thread Derek Hower
changeset 99ca47c2130b in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=99ca47c2130b description: merge diffstat: 164 files changed, 4889 insertions(+), 9219 deletions(-) src/arch/SConscript |3 src/ar

[m5-dev] Cron /z/m5/regression/do-regression quick

2009-07-13 Thread Cron Daemon
* build/ARM_SE/tests/fast/quick/00.hello/arm/linux/simple-atomic passed. * build/X86_SE/tests/fast/quick/00.hello/x86/linux/simple-timing-ruby passed. * build/X86_SE/tests/fast/quick/00.hello/x86/linux/simple-atomic passed. * build/X86_SE/tests/fast/quick/00.hello/x86/linux/simple-