Re: [gem5-users] LSQ bottleneck when using X86 TSO

2014-05-13 Thread Steve Reinhardt via gem5-users
I just posted the patch for review; see http://reviews.gem5.org/r/2277. It may depend on some of the other patches I posted immediately prior to it, particularly 2276. Steve On Mon, May 5, 2014 at 9:32 AM, Adrián Colaso Diego via gem5-users < gem5-users@gem5.org> wrote: > It sounds good, i wil

Re: [gem5-users] Segfault when changing renameWidth

2014-05-13 Thread Mitch Hayenga via gem5-users
PS: This issue was fixed about two weeks ago by putting in an assert to warn when MaxWidth was <= any width in the machine. So it's in the mainline, just not in gem5-stable. http://repo.gem5.org/gem5?cmd=changeset;node=790a214be1f4 On Tue, May 13, 2014 at 4:36 PM, Mitch Hayenga wrote: > Gem5

Re: [gem5-users] Clocksource tsc unstable

2014-05-13 Thread Joel Hestness via gem5-users
Hey guys, I tested this issue fairly thoroughly. My conclusion is that the 'clocksource=jiffies' kernel param fixes the clock instability issue, while other suggested solutions don't. It might be a good idea to shift over to clocksource= being the default param in FSConfig.py if people feel chec

Re: [gem5-users] Segfault when changing renameWidth

2014-05-13 Thread Mitch Hayenga via gem5-users
Gem5 has some hard compile-time limits on how large certain widths can be. In src/cpu/o3/impl.hh there is a line that sets "MaxWidth = 8". Increase this to greater than or equal to 16 (or whatever the maximum width in your machine is). The issue you are hitting is time buffer entries writing int

[gem5-users] Segfault when changing renameWidth

2014-05-13 Thread Jordan Fix via gem5-users
Hello, I believe I have found a bug in the O3 cpu model. I have simply adjusted the renameWidth from 8 to 16 in src/cpu/o3/O3CPU.py. Doing this causes the commit unit to seg fault at line 1286 in src/cpu/o3/commit_impl.hh. It appears the fromRename buffer size is incorrect (value of 55356032).

Re: [gem5-users] Writeback buffer kills O3 performance, what is it meant to model?

2014-05-13 Thread Mitch Hayenga via gem5-users
I actually wrote a patch a while back (apparently Feb 20) that fixed the load squash issue. I kind of abandoned it, but it was able to run a few benchmarks (never ran the regression tests on it). I'll revive that and see if it passes the regression tests. All it did was force the load to be repe

Re: [gem5-users] Writeback buffer kills O3 performance, what is it meant to model?

2014-05-13 Thread Vamsi Krishna via gem5-users
Hello All, As Paul was mentioning, I tried to come up with small analysis on how the number of writeback buffers affect performance of PARSEC benchmarks when increased by 5x the default size. I found out that 2-wide processor improved by 22% , 4-wide processor by 7% and 8-wide processor by 0.6% in