M_sequencer is the default handle for uvm_vitual_sequencer and m_sequencer is the HOOK up for child sequencer.

M_sequencer is the generic uvm_sequencer POINTER. It will always exist for the uvm_sequencer and is INITIALIZED when the sequence is STARTED.

P_sequencer is a typed-SPECIFIC sequencer pointer, created by registering the sequence to the sequencer using macros (`uvm_declare_p_sequencer) . Being type specific, you will be able to access anything added to the sequencer (i.e. pointers to other sequencers, etc.). M_sequencer will not exist if we have not registered the sequence with the `uvm_declare_p_sequencer macros.

The drawback of m_sequencer is that once the m_sequencer is defined, one cannot run the sequence on any other sequencer type.

M_sequencer is the default handle for uvm_vitual_sequencer and m_sequencer is the hook up for child sequencer.

M_sequencer is the generic uvm_sequencer pointer. It will always exist for the uvm_sequencer and is initialized when the sequence is started.

P_sequencer is a typed-specific sequencer pointer, created by registering the sequence to the sequencer using macros (`uvm_declare_p_sequencer) . Being type specific, you will be able to access anything added to the sequencer (i.e. pointers to other sequencers, etc.). M_sequencer will not exist if we have not registered the sequence with the `uvm_declare_p_sequencer macros.

The drawback of m_sequencer is that once the m_sequencer is defined, one cannot run the sequence on any other sequencer type.