cpu: Add support for protobuf input for the trace generator
Review Request #1577 - Created Dec. 6, 2012 and submitted
| Information | |
|---|---|
| Andreas Hansson | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 9372:2b774df97e24 --------------------------- cpu: Add support for protobuf input for the trace generator This patch adds support for reading input traces encoded using protobuf according to what is done in the CommMonitor. A follow-up patch adds a Python script that can be used to convert the previously used ASCII traces to protobuf equivalents. The appropriate regression input is updated as part of this patch.
util/regress all passing (disregarding t1000 and eio)
Issue Summary
1
1
0
0
| Description | From | Last Updated | Status |
|---|---|---|---|
| Can we not directly read a trace element? Creating a Packet seems unnecessary. | Nilay Vaish | Jan. 2, 2013, 11:37 p.m. | Open |
Review request changed
Updated (Dec. 11, 2012, 10:54 p.m.)
Description: |
|
|||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 2 (+38 -62) |
Posted (Jan. 2, 2013, 11:37 p.m.)
-
src/cpu/testers/traffic_gen/traffic_gen.cc (Diff revision 2) -
Can we not directly read a trace element? Creating a Packet seems unnecessary.