Jump to content

potential implementation issue in uvm_config_db

Recommended Posts


In the uvm_config_db source code, the m_rsc lookup table seems to work as a local cache for config settings.

Two issues here:

* It is never used in the uvm_config_db #(T) :: get ( ... ) interface method.

* In the uvm_config_db #(T) :: m_get_resource_match ( ... ) interface method, if the pool for the specified context has been allocated but the lookup = {inst_name, field_name} doesn't exists in the pool, null uvm_resource reference will be returned to uvm_config_db #(T) :: set (...) and anther pool object will be allocated and replaces the previously allocated pool. Then all the resource in the previously allocated pool will be dropped thoroughly.

However, the functionality of uvm_config_db will not be impacted at all due to the issue above.




Link to comment
Share on other sites


i would suggest to file a mantis item (as described in the .pdf) first. the viptsc does discuss the current mantis items during the regular calls and at the same time the issue is captured in a tracking system where also others can view those issue,


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