Re: [gem5-users] Fullsystem with NoC

2014-10-11 Thread babak aghaei via gem5-users
Hi this is possible, befor you must establish the garnet network and then run any benchmark on it. best --- Babak Aghaei Ph.D candidate From: Matheus Alcântara Souza via gem5-users To: "gem5-users@gem5.org" Sent: Saturday, Octobe

[gem5-users] (no subject)

2014-10-11 Thread babak aghaei via gem5-users
Hi this is possible, befor you must establish the garnet network and then run any benchmark on it. best --- Babak Aghaei Ph.D candidate ___ gem5-users mailing list gem5-users@gem5.org http://m

[gem5-users] Fullsystem with NoC

2014-10-11 Thread Matheus Alcântara Souza via gem5-users
Dear all, I've been reading the gem5 list for quite some time, with the goal of know how to run applications (such as PARSEC ones) in fullsystem mode, over a network-on-chip architecture. I concluded that this is not possible nowadays. So I wonder if I am wrong? If yes, what should I do to ru

Re: [gem5-users] ignore many simObjects from trace with --trace-ignore=EXPR

2014-10-11 Thread Steve Reinhardt via gem5-users
It's a little convoluted, but I think I found the problem. Apparently having multiple ignore strings hasn't worked in quite some time, if ever. In src/python/m5/main.py, the ignore strings are passed into C++ one at a time: for ignore in options.debug_ignore: check_tracing()

Re: [gem5-users] ignore many simObjects from trace with --trace-ignore=EXPR

2014-10-11 Thread Marcus Tshibangu via gem5-users
Thanks Steve, you are right I still have the old version with both debug* and trace* optons but it shouldn't make a difference. it maybe that the --trace-ignore option itself is not working for multiple objects only for one object. because even append doesn't work for it but it works for other opti

Re: [gem5-users] thread migration

2014-10-11 Thread Steve Reinhardt via gem5-users
The error you're seeing in your second email is precisely because you're no longer using drain(). Basically you're in trouble if you switch CPUs while there's a cache miss outstanding, because then the cache miss response will come back to the wrong (old) CPU. The point of drain() is to put the s

Re: [gem5-users] ignore many simObjects from trace with --trace-ignore=EXPR

2014-10-11 Thread Steve Reinhardt via gem5-users
Sometimes you've got to use the source... from src/python/m5/main.py: option("--debug-ignore", metavar="EXPR", action='append', split=':', help="Ignore EXPR sim objects") Apparently colon is supposed to be the delimiter. The 'split' option is a Nate extension (see src/python/m5/optio

[gem5-users] ignore many simObjects from trace with --trace-ignore=EXPR

2014-10-11 Thread Marcus Tshibangu via gem5-users
when I use *--trace-ignore='system.cpu0'*, I ignore everything related to cpu0 from trace file. but if I try *--trace-ignore='system.cpu0;system.cpu1' *hoping that I can ignore also cpu1, it doesn't work. what is the best separator for multiple simObjects in EXPR. I have tried comma, semicolon, col