Broadcasting reset assertion event via uvm_event_pool

In reply to sanoopvl:

Reset (and clock) signals should be part of your interfaces, and not passed through the UVM hierarchy. The reason for this is that each interface may use a separate reset (and clock), so you want your agent driver/monitor to be cognizant of it’s associated reset.

Stimulus generation should have no dependency on any reset. It is only when the sequence_item reaches the driver that the reset signal is considered. Your first set of sequence_items should occur at time 0.