Changes between Version 110 and Version 111 of Writing Rules/Tlmt

Timestamp:

Mar 2, 2009, 8:03:09 PM (15 years ago)

Author:

alain

Comment:

--

Writing Rules/Tlmt

@@ -19 +19 @@
 messages piggybacked with time information. This timing information is actually the absolute locat time of the sender. 
 Models complying to these TLM-T rules can be used with the "standard" OSCI simulation engine (SystemC 2.x) and
-the TLM2.0 library, but can also be used also with others simulation engines, especially distributed, parallelized simulation engines.
+the TLM2.0 library, but can also be used also with others simulation engines, especially parallelized simulation engines.
 
 The pessimistic PDES algorithm relies on temporal filtering of the incoming messages. A PDES process that has N input channels
@@ -27 +27 @@
 Moreover, all processes can be in two modes : active & non-active. Only processes that are active participate to the temporal filtering.
 
-A first implementation of TLMT used sollicited null messages, but the final solution uses direct null-messages, that strictly 
+A first implementation of TLMT used ''sollicited null messages'', but the final solution uses ''direct null-messages'', that strictly 
 follow the Chandy-Misra pessimistic algorithm. Each process cannot run independantly without sending a timed message
 for a time larger that a predefined value, called the SYNCHRONIZATION_TIME_QUANTUM. When this time quantum is elapsed,
 the process must send a null message on its output ports.
 
-The models described with the writing rules defined herein are syntactically compliant with the TLM2.0 standard, but do
-not respect its semantics. In particular, the third time parameter of the transport functions is considered to be an absolute
-time and not relative to a global simulation time that does prevail anymore.
+The models following the writing rules defined herein are syntactically compliant with the TLM2.0 standard, but have a different
+representation for the time. In particular, the third parameter of the transport functions is considered to be an absolute
+(but local) time and is not an offset relative to a global simulation time that is not used anymore.
  
 The examples presented below use the VCI/OCP communication protocol selected by the SoCLib project,