CR-1159280: Fixing profiling table to correctly associate argument with connection

[jvillarre]

Problem solved by the commit

Profiling tables that report data movement between kernels and memory report the original kernel arguments associated with the connection. With connections to host memory via host bridge, this association was not correctly made and the tables had empty entries. Additionally, if multiple kernels were present in a design and had arguments with the same name, they were incorrectly being reported as attached to the wrong memory component.

Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered

The issue was discovered through comprehensive regression testing.

How problem was solved, alternative solutions (if any) and why they were rejected

This change explicitly adds a check for host bridge connections. Additionally, it changes the argument to memory mapping data structure to make the connection on a compute unit basis rather than a kernel basis, so multiple kernels with identical named arguments don't overwrite each other.

Risks (if any) associated the changes in the commit

Low risk as this should only affect information reported in a single table.

What has been tested and how, request additional testing if necessary

Tested on original failing test case.

Documentation impact (if any)

No documentation impact

[gbuildx]

Build failed :(

[dayeh-xilinx]

retest this please.

[gbuildx]

Build failed :(

[manikandan-xilinx]

retest this please.

[gbuildx]

Build Passed!

[IshitaGhosh]

Change looks good