Jump to content

use of all_dropped callback in uvm_objection

Recommended Posts


I have found that all_dropped has been defined as a callback in uvm which user can extend and modify. But all of the functionality required is alredy defined inside all_dropped() function. So why was it made as a callback? What additional logics could be written inside this all_dropped callback.


Ranjith S

Link to comment
Share on other sites


Thanks a lot for your SeanChou.

I was trying to understand this objection area in more detail. My basic doubt was that what was the intention of the uvm source code developers to make the all_dropped as a callback?

What are all the things that they think to be added besides the source code in all_dropped function?

Link to comment
Share on other sites


the baseline scenario for objections (voting/consensus) is a barrier with N participating objects. apart from the "uvm_test_done" barrier with a result of "ending a simulation" you could have barriers to progress your test scenario from one phase (lets say config) to a new phase (lets say data-traffic), or you could use a custom objection to have traffic send as long as necessary - once all agree a particular device doesnt need to send traffic anymore you switch it off via all_objections_dropped



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...