potential implementation issue in uvm_config_db

[Robert.g.Liu]

Hi,

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.

Thanks,

Robert

www.lsi.com

[uwes]

hi,

can you please file a mantis (bug report/question/suggestion with the uvm bcl) here http://eda.org/svdb/bug_report_advanced_page.php? this is the primary errata database for uvm and might also have infos about already filed issues (or resolved issues)

/uwe

[Robert.g.Liu]

Hi uwe,

Ok. I will report the issues to vip-tc@lists.accellera.org first to get them discussed first.

-Robert

Edited March 10, 2011 by Robert.g.Liu

[uwes]

hi,

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,

/uwe