Changes between Version 39 and Version 40 of Writing Rules/Tlmt

Timestamp:

Feb 19, 2008, 9:12:23 PM (17 years ago)

Author:

fpecheux

Comment:

--

Writing Rules/Tlmt

@@ -11 +11 @@
 
 This document describes the modeling rules for writing TLM-T SystemC simulation models for SoCLib. 
-These rules enforce the PDES (Parallel Discrete Event Simulation) principles. Each PDES process involved in the simulation has its own local time, and PDES processes synchronize through messages piggybacked with time information.
+These rules enforce the PDES (Parallel Discrete Event Simulation) principles. Each PDES process involved in the simulation has its own local time, and PDES processes synchronize through messages piggybacked with time information. The process time, as well as other useful process attributes, is contained in a C++ structure called a '''thread context'''.
 Models complying to these rules can be used with the "standard" OSCI simulation engine (SystemC 2.x), but can also be used also with others simulation engines, especially distributed, parallelized simulation engines.
 
@@ -18 +18 @@
 = B) Single VCI initiator and single VCI target =
 
-Figure 1 presents a minimal system containing one single initiator, '''my_initiator''' , and one single target, '''my_target''' . The '''my_initiator''' module behavior is modeled by the SC_THREAD  '''execLoop()''', that contains an infinite loop.  The call-back function '''rspReceived()''' is executed when a VCI response packet is received by the initiator module.
+Figure 1 presents a minimal system containing one single initiator, '''my_initiatorVciSimpleInitiator''' , and one single target, '''my_targetVciSimpleTarget''' . The '''my_initiatorVciSimpleInitiator''' module behavior is modeled by the SC_THREAD  '''execLoop()''', that contains an infinite loop.  The call-back function '''rspReceived()''' is executed when a VCI response packet is received by the initiator module.
 
 [[Image(tlmt_figure_1.png, nolink)]]
 
-Unlike the initiator, the target module has a purely reactive behaviour.
-There is no need to use a SC_THREAD : The target behaviour is entirely described by the call-back function '''cmdReceived()''',
+Unlike the initiator, the target module has a purely reactive behaviour and is therefore modeled as a call-back function.
+Actually, there is no need to use a SC_THREAD : The target behaviour is entirely described by the call-back function '''cmdReceived()''',
 that is executed when a VCI command packet is received by the target module.
 
@@ -30 +30 @@
 = C) VCI initiator Modeling =
 
-In the proposed example, the initiator module is modeled by the '''my_initiator''' class. This class inherits from the '''!BaseModule''' class, that acts as the root classe for all TLM-T modules. As there is only one thread in this module, there is only one member variable '''m_time''' of type '''tlmt_time''', corresponding to the PDES process local time ('''H''' on the figure). This '''m_time''' object can be accessed through the '''getTime()''', '''addTime()''' and '''setTime()''' methods. 
+In the proposed example, the initiator module is modeled by the '''my_initiator''' class. This class inherits from the '''!BaseModule''' class, that acts as the root class for all TLM-T modules. As there is only one thread in this module, there is only one member variable '''m_time''' of type '''tlmt_time''', corresponding to the PDES process local time ('''H''' on the figure). This '''m_time''' object can be accessed through the '''getTime()''', '''addTime()''' and '''setTime()''' methods. 
 
 The '''execLoop()''' method, describing the initiator activity must be declared as a member function of the '''my_initiator''' class.