Ignore:
Timestamp:
Jun 16, 2015, 9:24:36 PM (9 years ago)
Author:
cfuguet
Message:

reconf: introducing a hardware barrier in the global-local interface of
the local interconnects.

  • This barrier is controlled by a port (barrier enable) in the dspin and vci local interconnects.
  • The barrier enable port is connected to a configuration register of the XICU component to allow the software to control this barrier. The barrier is enabled when the barrier enable port value is different of 0xFFFFFFFF. As the configuration register of the XICU component are reset to 0, this barrier is enabled by default.
  • This barrier allows to isolate the cluster from the rest of the architecture and only if it self-diagnoses as functional, it release the barrier to communicate with the others.
  • The same barrier enable signal is connected to the five local interconnects. Therefore, either all are released or all are disabled.
  • If a local initiator or an external initiator sends a packet out or into the cluster respectively, and the barrier is enabled, the packet is dropped.
File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/reconfiguration/modules/dspin_local_crossbar/caba/source/include/dspin_local_crossbar.h

    r977 r1001  
    7070        DspinOutput<flit_width>*        p_local_out;
    7171
     72        sc_in<uint32_t>                *p_barrier_enable;
     73
    7274        void      print_trace();
    7375
     
    8688                            const bool          is_cmd,
    8789                            const bool          use_routing_table,
    88                             const bool          broadcast_supported );
     90                            const bool          broadcast_supported,
     91                            const bool          hardware_barrier = false );
    8992
    9093        ~DspinLocalCrossbar();
Note: See TracChangeset for help on using the changeset viewer.