----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3090/#review7665 -----------------------------------------------------------
src/cpu/o3/probe/elastic_trace.hh (lines 357 - 359) <http://reviews.gem5.org/r/3090/#comment6611> Do we really need this? I would rather always trace the virtual address as well. I don't think there are any code correctness or clarity or performance gains to be made from this check. - Nilay Vaish On Sept. 3, 2015, 4:17 p.m., Curtis Dunham wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/3090/ > ----------------------------------------------------------- > > (Updated Sept. 3, 2015, 4:17 p.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > This patch adds support to optionally capture the virtual address and asid > for load/store instructions in the elastic traces. If they are present in > the traces, Trace CPU will set those fields of the request during replay. > > This patch adds to the "Elastic Traces" patch series of RB3026-3031,3089. > > > Diffs > ----- > > src/cpu/o3/probe/ElasticTrace.py PRE-CREATION > src/cpu/o3/probe/elastic_trace.hh PRE-CREATION > src/cpu/o3/probe/elastic_trace.cc PRE-CREATION > src/cpu/trace/trace_cpu.hh PRE-CREATION > src/cpu/trace/trace_cpu.cc PRE-CREATION > src/proto/inst_dep_record.proto PRE-CREATION > util/decode_inst_dep_trace.py PRE-CREATION > util/encode_inst_dep_trace.py PRE-CREATION > > Diff: http://reviews.gem5.org/r/3090/diff/ > > > Testing > ------- > > > Thanks, > > Curtis Dunham > > _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
