> On Sept. 18, 2013, 6:39 p.m., Nilay Vaish wrote:
> > Any comments? I am planning to commit it on Friday.
>
> Andreas Hansson wrote:
> Do any regressions change?
>
> Would it be an option to change the aforementioned functionality so that
> what ever is causing the issue does not
> On Nov. 15, 2013, 5:34 a.m., Steve Reinhardt wrote:
> > Seems like it would be simpler just to move the stats.reset() call inside
> > the 'if need_startup:' block, right?
Yes
- Nilay
---
This is an automatically generated e-mail. To
> On Nov. 13, 2013, 2:24 p.m., Mihai Lefter wrote:
> > Currently I was also looking into this issue (adding an extra write latency
> > actually). As far as I can see this patch considers a different write
> > latency only for write operations that come from the CPU side, i.e., on the
> > cpuSi
scons: `build/NULL/gem5.debug' is up to date.
scons: `build/NULL/gem5.fast' is up to date.
scons: `build/ALPHA_MOESI_hammer/tests/opt/quick/fs' is up to date.
scons: `build/ALPHA_MESI_CMP_directory/tests/opt/quick/fs' is up to date.
scons: `build/ALPHA_MOESI_CMP_directory/tests/opt/quick/fs' is up
