Hi Folks,
I’ve just started using Nsight System and it’s real handy! Unfortunately, in the trace collected, none of the linux kernel symbols are resolved.
I am using a v6.8 kernel with custom compiled nvidia drivers from source, /proc/sys/kernel/kptr_restrict is set to zero and /proc/kallsyms available for reading as non-root user (I did even try to run nsys as root but got the same result).
The host I’m viewing the collected traces on is a MacOS - not the target device with the GPU.
Any help in this regard would be appreciated :)
Thanks in advance!
Q
@rknight can you help with this one?
Unfortunately, Nsight Systems doesn’t support resolving kernel symbols yet.
Many thanks @hwilper and @rknight for your quick asnwer here.
Unfortunately, Nsight Systems doesn’t support resolving kernel symbols yet.
That is really surprising, from the screenshot attached to this other forum post we can see Nsight Systems showing the symbol _raw_spin_unlock_irq() - am I missing something?
Thanks in advance for your help!
Sorry, I should have specified that on x86_64 and SBSA based Linux systems, Nsight Systems doesn’t support resolving kernel symbols yet.
Interesting - would you know if this a limitation introduced on purpose?
As I understand it, resolving symbols from the Linux kernel is not architecture dependent, one needs to find the corresponding symbol in /proc/kallsyms if available and kptr_restrict is disabled, so if this is supported on Jetson it should equally work on other architectures unless I’m missing something.