[gem5-dev] changeset in gem5: minor: fixed LSQ MasterPortID

2015-01-04 Thread Andrew Lukefahr via gem5-dev
changeset c5a2c5ef6e68 in /z/repo/gem5 details: http://repo.gem5.org/gem5?cmd=changeset;node=c5a2c5ef6e68 description: minor: fixed LSQ MasterPortID Minor was reporting the data cache access as ".inst" accesses. This just switches the MasterPortID to dataMasterPortId.

[gem5-dev] Review Request 2474: minor: fixed LSQ MasterPortID

2014-11-10 Thread Andrew Lukefahr via gem5-dev
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2474/ --- Review request for Default. Repository: gem5 Description --- Changeset 10540

[gem5-dev] changeset in gem5: cpu: Minor Draining Bug

2014-11-06 Thread Andrew Lukefahr via gem5-dev
changeset d0c2ba70dc12 in /z/repo/gem5 details: http://repo.gem5.org/gem5?cmd=changeset;node=d0c2ba70dc12 description: cpu: Minor Draining Bug Fixes a bug where Minor drains in the midst of committing a conditional store. While committing a conditional store, lastC

Re: [gem5-dev] Review Request 2470: cpu: Minor Draining Bug

2014-10-29 Thread Andrew Lukefahr via gem5-dev
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2470/ --- (Updated Oct. 29, 2014, 3:01 p.m.) Review request for Default. Repository: gem5

Re: [gem5-dev] Review Request 2470: cpu: Minor Draining Bug

2014-10-29 Thread Andrew Lukefahr via gem5-dev
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2470/ --- (Updated Oct. 29, 2014, 3:01 p.m.) Review request for Default. Repository: gem5

[gem5-dev] Review Request 2470: cpu: Minor Draining Bug

2014-10-29 Thread Andrew Lukefahr via gem5-dev
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2470/ --- Review request for Default. Repository: gem5 Description --- Changeset 10510

[gem5-dev] changeset in gem5: cpu: Fix o3 SMT IQCount bug

2014-10-11 Thread Andrew Lukefahr via gem5-dev
changeset 933cc91f63e1 in /z/repo/gem5 details: http://repo.gem5.org/gem5?cmd=changeset;node=933cc91f63e1 description: cpu: Fix o3 SMT IQCount bug Commmitted by: Nilay Vaish diffstat: src/cpu/o3/fetch_impl.hh | 12 ++-- 1 files changed, 10 insertions(+), 2 deletions(-)

[gem5-dev] changeset in gem5: sim: draining bug for fast-forwaring multiple...

2014-10-11 Thread Andrew Lukefahr via gem5-dev
changeset bdb307e8be54 in /z/repo/gem5 details: http://repo.gem5.org/gem5?cmd=changeset;node=bdb307e8be54 description: sim: draining bug for fast-forwaring multiple cores fix draining bug where multiple cores hit max_insts_any_thread simultaneously Committed by: Nilay Vais

Re: [gem5-dev] Review Request 2400: smt: Fixed IQCount bug

2014-09-15 Thread Andrew Lukefahr via gem5-dev
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2400/ --- (Updated Sept. 15, 2014, 6:29 p.m.) Review request for Default. Summary (updated)

Re: [gem5-dev] Review Request 2400: Fixed IQCount bug

2014-09-15 Thread Andrew Lukefahr via gem5-dev
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2400/ --- (Updated Sept. 15, 2014, 6:02 p.m.) Review request for Default. Summary (updated)

[gem5-dev] Review Request 2400: IQCount Patch

2014-09-10 Thread Andrew Lukefahr via gem5-dev
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2400/ --- Review request for Default. Repository: gem5 Description --- Changeset 10366

Re: [gem5-dev] Review Request 2228: sim: draining bug for fast-forwaring multiple cores

2014-05-30 Thread Andrew Lukefahr via gem5-dev
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2228/ --- (Updated May 30, 2014, 2:20 p.m.) Review request for Default. Repository: gem5

Re: [gem5-dev] Review Request 2228: sim: draining bug for fast-forwaring multiple cores

2014-05-20 Thread Andrew Lukefahr via gem5-dev
> On April 30, 2014, 3:13 a.m., Ali Saidi wrote: > > Thanks for the patch Andrew. > > > > My only hesitation is that this does seem to create another issue (probably > > a less likely one) where the simulator could try to really exit here and > > fail. That said it's probably good to fix this