On Feb. 3, 2015, 9:37 p.m., Brandon Potter wrote:
The patch seems like a landmine for an unsuspecting user as it would be
difficult to diagnose if swap space is exhausted. It will probably be
evident that memory exhaustion caused the runtime error (segmentation
fault), but tracking
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2646/
---
(Updated Feb. 8, 2015, 5:48 p.m.)
Review request for Default.
Repository: gem5
On Feb. 7, 2015, 6:14 p.m., Steve Reinhardt wrote:
Awesome! This lack of separate channels for requests responses has
bugged me for years, I'm really glad to see it addressed.
One minor suggestion: to me, terms like recvRetryReq and recvRetryResp seem
backward, since 'retry' is
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2650/
---
Review request for Default.
Repository: gem5
Description
---
Changeset
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2651/
---
Review request for Default.
Repository: gem5
Description
---
Changeset
* build/ALPHA/tests/opt/quick/se/30.eio-mp/alpha/eio/simple-timing-mp
passed.
* build/ALPHA/tests/opt/quick/se/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/tru64/minor-timing passed.
*
