> On Juni 22, 2015, 8:16 nachm., Nilay Vaish wrote: > > I think I sort of understand what is going on in the patch. It is > > fine by me if we commit this patch, more so since the changes only > > affect a couple of files in configs/common. > > > > Just for my understanding, suppose I want to model a new component that > > communicates through some sort of transaction. And I want that this > > component > > be written in SystemC and the rest of the system simulation infrastructure > > be provided by gem5. Would I have to change the sc_target class to > > implement > > the functionality of this new component?
Exactly the sc_target is basically a simple memory stub, which can be exchanged by any TLM 2.0 compliant model. - Matthias ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2753/#review6554 ----------------------------------------------------------- On Juni 19, 2015, 10:36 nachm., Matthias Jung wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/2753/ > ----------------------------------------------------------- > > (Updated Juni 19, 2015, 10:36 nachm.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > Changeset 10873:2fdd00daa012 > --------------------------- > misc: Coupling gem5 with SystemC TLM2.0 > Transaction Level Modeling (TLM2.0) is widely used in industry for creating > virtual platforms (IEEE 1666 SystemC). This patch contains a standard > compliant > implementation of an external gem5 port, that enables the usage of gem5 as a > TLM initiator component in SystemC based virtual platforms. Both TLM coding > paradigms loosely timed (b_transport) and aproximately timed (nb_transport) > are > supported. > > Compared to the original patch a TLM memory manager was added. Furthermore, > the transaction object was removed and for each TLM payload a PacketPointer > that points to the original gem5 packet is added as an TLM extension. > > > Diffs > ----- > > configs/common/MemConfig.py 9141d87c7f71 > configs/common/Options.py 9141d87c7f71 > util/tlm/Makefile PRE-CREATION > util/tlm/README PRE-CREATION > util/tlm/main.cc PRE-CREATION > util/tlm/run_gem5.sh PRE-CREATION > util/tlm/sc_ext.hh PRE-CREATION > util/tlm/sc_ext.cc PRE-CREATION > util/tlm/sc_mm.hh PRE-CREATION > util/tlm/sc_mm.cc PRE-CREATION > util/tlm/sc_port.hh PRE-CREATION > util/tlm/sc_port.cc PRE-CREATION > util/tlm/sc_target.hh PRE-CREATION > util/tlm/sc_target.cc PRE-CREATION > util/tlm/tgen.cfg PRE-CREATION > util/tlm/tlm.py PRE-CREATION > > Diff: http://reviews.gem5.org/r/2753/diff/ > > > Testing > ------- > > > Thanks, > > Matthias Jung > > _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
