Open suyashmahar opened 2 months ago
Hi @suyashmahar,
In the examples/high-level-api/mem_move_example.cpp
, could you please also print out result.status
right before "Failure occurred" message?
Hi @mzhukova,
I got 16
:
Hi @mzhukova , are there any env flags / build configuration I can use to debug this issue? Thanks for the help!
@mzhukova, I think I found the reason. If DML cannot find libaccel-config.so, it just reports an internal error. I confirmed this using strace.
Any HW initialization failure in this code is reported as a generic failure. If the "if" condition fails.
This is where the library tries to load libaccel-config.so
If I make sure that libaccel-config.so is accessible, the hardware_path example works.
Sorry for the delayed response @suyashmahar. I'm glad that you were able to find the root cause of the failure. We will work on improving the status reporting in one of the future releases.
I'm unable to use the HW path for mem move even after configuring the DSA devices:
When manually calling dml::memmove, I get error code 16 that corresponds to internal library error. Is there a way to debug this? Any help would be really appreciated. Thanks!
System Configuration
Processor: Intel(R) Xeon(R) Silver 4416+
I have configured DSA using the python script:
I'm also running relatively recent kernel version:
Kernel cmdline:
lspci
output for one of the two devices available: