Jump to content

Calling put_response when sequence that initiated sequence item has terminated

Recommended Posts

What happens when a driver calls seq_item_port.put_response() with a response associated a request sequence item where the sequence that sent the request sequence item has terminated (and taken its response queue with it)?


I'm not talking about a programming error condition where the sequence shouldn't have terminated.  I'm talking about a real use case where the sequence did not want to wait for the response.  And there would be other sequences working with this driver that did want to wait for and get their responses.


It seems to be "handled" by the UVM code.  Presumably the code under the hood for put_response sees that the response queue (or sequence) is no longer running and just does nothing.


I'm wondering if this is intentional in the UVM implementation, and an expected usage model, or I'm just getting lucky and the current implementation happens to work for me.






Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...