The scope of accessibility for uvm_config_db::set and uvm_config_db::get methods

UVM
1

Hi
Regarding uvm_config_db set and get methods, I quote the following from verificationguide.com:


void uvm_config_db#(type T = int)::set(uvm_component cntxt, string inst_name, string field_name, T value);
bit uvm_config_db#(type T=int)::get(uvm_component cntxt, string inst_name, string field_name, ref T value);

Where,
...
cntxt is the hierarchical starting point of where the database entry is accessible.
inst_name is a hierarchical path that limits the accessibility of the database entry.
...

Does this mean that the scope of accessibility will be a single instance whose path is given by {cntxt,”.”,inst_name} as mentioned in the standard, or it will be a range, starting from cntxt, all the way down to inst_name, possibly covering many instances in between?
Thank you

2

In reply to Farhad:
example given in same link:
top.env.agent.monitor
top.* – all of the scopes whose top-level component is top.
top.env.*.monitor – all of the scopes in env that end in the monitor;

if we use below method then it’s a universal access
uvm_config_db#(type T = int)::set(null,“*”,“field_name”, value);
i.e. you can below method get teh value of filed_name any where in testbench

uvm_config_db#(type T = int)::get(null,“*”,“field_name”, value);

{cntxt,”.”,inst_name} : gives flexibility to access permissions using wild card “*” or direct hard coded path
Hope it’s clear