m_parent in ubus example

[chenyong]

Hi,

I found some code with method/variant "m_parent" in uvm-1.1 example of ubus. I can't find this m_parent definition in the code and can't find related infomation in the class reference. Can anybody give me some help? thanks.

[Roman]

Hi There,

As I understand.

Based on the layering hierarchy graph of ubus example, Each instance is a node connected to others to form the graph. Hierarchy is overlaid with m_parent.

The m_parent in the ubus_master_monitor points to ubus_master_agent instance in the ubus_env.

Hope this help you~

[chenyong]

Hi There,

As I understand.

Based on the layering hierarchy graph of ubus example, Each instance is a node connected to others to form the graph. Hierarchy is overlaid with m_parent.

The m_parent in the ubus_master_monitor points to ubus_master_agent instance in the ubus_env.

Hope this help you~

Hi Roman,

thanks for your reply.

1) does this mean if I see m_parent in monitor, then I know it points to env?

2) does this mean m_parent is a "default defintion" in UVM?

thanks

[Roman]

for #1: m_parent is a build-in pointer to the parent component

for #2: I think m_parent is a build-in in UVM

[chenyong]

thank you very much

[janick]

Avoid using any undocumented variable or method, especially if prefixed with "m_". Since SystemVerilog does not support friend classes, they are public for implementation reasons. They are not part of the standard and are subject to removal/renaming/modification.

Use uvm_component::get_parent().

[Roman]

Agree!

m_parent occurs in example of UVM pkg, it will mislead guys who may study UVM based on ubus example.

I think m_parent should be removed from example of UVM pkg.

[chenyong]

thanks for this information. Is there any other "code" which is not supported by standard but appear in the example?

[uwes]

hi,

in case the examples use internal capabilities it should be considered a bug and will be removed in subsequent releases.

/uwe

[Roman]

thanks for this information. Is there any other "code" which is not supported by standard but appear in the example?

Hi,

In the ubus example: assign_vif function is used.

But this approach is not recommended because of lack of reuse when hierarchy is changing from project to project.

I recommend to use the uvm_config_db utility to transmit the vif or cfg obj crossing the hierarchy.

[chenyong]

HI,

I guess this is true. In UVM-1.1, I can't find assign_vif but uvm_config_db. It is said uvm-1.2 will come soon, don't know what will be changed at that time.

[Roman]

HI,

I guess this is true. In UVM-1.1, I can't find assign_vif but uvm_config_db. It is said uvm-1.2 will come soon, don't know what will be changed at that time.

UVM1.2 may be released around DVcon2012