---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2874/
---
(Updated July 6, 2015, 11:43 a.m.)
Review request for Default.
Repository: gem5
On July 4, 2015, 7:57 p.m., Steve Reinhardt wrote:
So I think the Drainable class is a great idea, it's nice not to pollute
random SimObjects with code that forces them to track what sub-objects of
theirs need to be drained.
I'm less convinced about the benefits of irreversibly
On July 4, 2015, 11:57 a.m., Steve Reinhardt wrote:
So I think the Drainable class is a great idea, it's nice not to pollute
random SimObjects with code that forces them to track what sub-objects of
theirs need to be drained.
I'm less convinced about the benefits of irreversibly
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2874/#review6704
---
So I think the Drainable class is a great idea, it's nice not to pollute
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2874/#review6695
---
Ship it!
Ship It!
- Nilay Vaish
On June 8, 2015, 12:13 p.m., Andreas
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2874/#review6632
---
I'll read the patch once more after you have answered my queries,
On June 27, 2015, 6:44 p.m., Nilay Vaish wrote:
src/python/m5/simulate.py, line 335
http://reviews.gem5.org/r/2874/diff/1/?file=46098#file46098line335
Why do we not need this resume()?
Resume is now called automatically by simualte() if simulate is called on a
drained system. We
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2874/
---
Review request for Default.
Repository: gem5
Description
---
Changeset
