Changes between Version 58 and Version 59 of Writing Rules/Tlmt

Timestamp:

Nov 15, 2008, 2:37:26 PM (18 years ago)

Author:

alain

Comment:

--

Writing Rules/Tlmt

@@ -86 +86 @@
   tlm::tlm_sync_enum nb_transport_fw               /// sync status
   ( soclib_vci_types::tlm_payload_type &payload,      ///< VCI payload pointer
-    soclib_vci_types::tlmt_phase_type   &phase,       ///< transaction phase
+    soclib_vci_types::tlm_phase_type   &phase,       ///< transaction phase
     sc_core::sc_time                   &time);        ///< time
 }}}
@@ -95 +95 @@
 To prepare a VCI packet for sending, the '''execLoop''' function must declare two objects locally, '''payload''' and '''phase'''.
 {{{
-  soclib_vci_types::vci_payload_type payload;
-  soclib_vci_types::tlmt_phase_type phase;
-}}}
-A payload of type '''soclib_vci_types::vci_payload_type''' corresponds to a '''tlmt_vci_transaction''' and thus
-contains three kinds of structure fields: TLM2.0 related fields,VCI related fields, and TLM-T related fields. 
-
-The contents of a '''tlmt_transaction''' is defined below:
+  soclib_vci_types::tlm_payload_type payload;
+  soclib_vci_types::tlm_phase_type phase;
+}}}
+A payload of type '''soclib_vci_types::tlm_payload_type''' corresponds to a '''tlmt_vci_transaction'''.
+It contains three groups of information: 
+ * TLM2.0 related fields
+ * TLM-T related fields 
+ * VCI related fields 
+The contents of a '''tlmt_vci_transaction''' is defined below:
 {{{
 class tlmt_vci_transaction
@@ -118 +120 @@
   unsigned int         m_streaming_width;       // 
 
+  // TLM-T related fields
+  
+  bool*                m_activity_ptr;
+  sc_core::sc_time*    m_local_time_ptr;
+
   // VCI related fields
   
@@ -124 +131 @@
   unsigned int         m_trd_id;                // trdid
   unsigned int         m_pkt_id;                // pktid
-
-  // TLM-T related fields
-  
-  bool*                m_activity_ptr;
-  sc_core::sc_time*    m_local_time_ptr;
-
 }}}
 
@@ -135 +136 @@
 array pointer and its associated size in bytes, and the data array pointer and its associated size in bytes. The byte
 enable array allows to build versatile packets thanks to a powerful but slow data masking scheme. Further experiments are
-currently done. It is likely that the types of the '''m_data''' and '''m_byte_enable''' of the '''tlmt_vci_transaction'''
+currently done to evaluate the performance degradation incurred by the byte formatting.
+It is therefore  possible that the types of the '''m_data''' and '''m_byte_enable''' of the '''tlmt_vci_transaction'''
 will be changed to '''uint32*''' in a near future.
 
-The VCI accessors are used to define the VCI transaction type, that can either be '''set_read()''' (for read command),
+Dedicated VCI accessors are used to define the VCI transaction type, that can either be '''set_read()''' (for read command),
 '''set_write()''' (for write command),'''set_locked_read()''' (for atomic locked read), 
 and '''set_store_cond()''' (for atomic store conditional). The '''set_src_id()''', '''set_trd_id()''' and '''set_pkt_id()''' functions 
 respectively set the VCI source, thread and packet identifiers.
-
+The following example describes a VCI write command:
 {{{
     payload.set_address(0x10000000);//ram 0
@@ -163 +165 @@
 
 The '''nb_transport_fw()''' function is non-blocking. 
-To implement a blocking transaction (such as a cache line read, where the processor is ''frozen'' during the VCI transaction), 
+To implement a blocking transaction (such as a cache line read, where the processor is stalled during the VCI transaction), 
 the model designer must use the SystemC '''sc_core::wait(x)''' primitive ('''x''' being of type '''sc_core::sc_event'''): 
 the '''execLoop()''' thread is then suspended, and will be reactivated when the response packet is actually received.