Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
4995 Discussions

Is the Intel Icelake supported by vTune?

soderstrom__carl
1,565 Views

insmod /mnt/disk0/vtune/sepdk/src/pax/pax-x32_64-4.18.45-yocto-standardsmp.ko

insmod: ERROR: could not insert module /mnt/disk0/vtune/sepdk/src/pax/pax-x32_64-4.18.45-yocto-standardsmp.ko: Unknown symbol in module

root@firepower-4245:/asa/scripts# dmesg -c
[11021.209102] pax: Unknown symbol __x86_indirect_thunk_rax (err 0)
root@firepower-4245:/asa/scripts#

uname -a

Linux firepower-4245 4.18.45-yocto-standard #1 SMP Fri Oct 16 19:16:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

root@firepower-4245:~# more /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 106
model name : Genuine Intel(R) CPU $0000%@
stepping : 4
microcode : 0x8b000015
cpu MHz : 2700.042
cache size : 36864 KB
physical id : 0
siblings : 48
core id : 0
cpu cores : 24
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 27
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc t tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local wbnoinvd dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req avx512vbmi umip pku avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq rdpid md_clear pconfig flush_l1d arch_capabilities
bugs : spectre_v1 spectre_v2 spec_store_bypass swapgs
bogomips : 5400.00
clflush size : 64
cache_alignment : 64
address sizes : 52 bits physical, 57 bits virtual
power management:

Self Checker Script doesn't seem to work:

root@firepower-4245:/mnt/disk0/vtune# /mnt/disk0/vtune/bin64/vtune-
vtune-agent vtune-self-checker.sh
vtune-backend vtune-set-perf-caps.sh
vtune-gui vtune-worker
vtune-gui.desktop vtune-worker-crash-reporter
vtune-pgo-report.sh
<tune# /mnt/disk0/vtune/bin64/vtune-self-checker.sh
Traceback (most recent call last):
File "/opt/cisco/csp/applications/cisco-asa.99.17.1.33__asa_001_JMX2333X18V3CS6KH1/app_data/disk0/vtune/bin64/self_check.py", line 777, in <module>
ret_code = main()
File "/opt/cisco/csp/applications/cisco-asa.99.17.1.33__asa_001_JMX2333X18V3CS6KH1/app_data/disk0/vtune/bin64/self_check.py", line 728, in main
state = State(bin_dir, work_dir)
File "/opt/cisco/csp/applications/cisco-asa.99.17.1.33__asa_001_JMX2333X18V3CS6KH1/app_data/disk0/vtune/bin64/self_check.py", line 167, in __init__
self.write_header()
File "/opt/cisco/csp/applications/cisco-asa.99.17.1.33__asa_001_JMX2333X18V3CS6KH1/app_data/disk0/vtune/bin64/self_check.py", line 257, in write_header
build_number = self.get_build_number()
File "/opt/cisco/csp/applications/cisco-asa.99.17.1.33__asa_001_JMX2333X18V3CS6KH1/app_data/disk0/vtune/bin64/self_check.py", line 244, in get_build_number
if support_path:
UnboundLocalError: local variable 'support_path' referenced before assignment

Log location: /tmp/vtune-tmp-root/self-checker-2020.05.12_15.06.37/log.txt


cat /tmp/vtune-tmp-root/self-checker-2020.05.12_15.06.37/log.txt
Cannot find 'support.txt' by path: /opt/cisco/csp/applications/cisco-asa.99.17.1.33__asa_001_JMX2333X18V3CS6KH1/app_data/disk0/vtune/support.txt

Log location: /tmp/vtune-tmp-root/self-checker-2020.05.12_15.06.37/log.txt

0 Kudos
1 Solution
soderstrom__carl
1,421 Views

Hi -

Yes we traced it down to a compile tool chain issue. Once we got by that we could load the kernel mods. Then we got stuck on our vtune version not working with the "pre-production" Icelakes we are using. We downloaded the NDA version and I think we are all set.

We can close this case. Thanks

View solution in original post

8 Replies
Viet_H_Intel
Moderator
1,555 Views

We have an NDA version which supports Icelake.


0 Kudos
soderstrom__carl
1,535 Views

What's an NDA version? Non released?

We thought that 2020 update 3 supported Icelake.

Can you look at the error I'm getting and tell if it's a problem with Icelake or something else?

Thanks

0 Kudos
JananiC_Intel
Moderator
1,499 Views

Hi,


Thanks for the update.


NDA is Non Disclosure Agreement and Vtune Icelake server seems to be under NDA. So we would like to know whether you are using desktop or server.Also Icelake is supported with vtune update 3.

Regarding the error,we need your complete log to figure out the issue.


Regards,

Janani Chandran






0 Kudos
soderstrom__carl
1,495 Views

I'm at Cisco. We are evaluating the intel Icelake for one of our firewall products. I know if you would call that a client or a server. Typically this would called an embedded system application.

Please specify what "complete logs" means and/or just tell me what you want to see.

Thanks

0 Kudos
Kirill_U_Intel
Employee
1,482 Views

Hi,

vtune-self-checker.sh issue:

Does it /opt/cisco/csp/applications/cisco-asa.99.17.1.33__asa_001_JMX2333X18V3CS6KH1/app_data/disk0/vtune official install? issue reported that /opt/cisco/csp/applications/cisco-asa.99.17.1.33__asa_001_JMX2333X18V3CS6KH1/app_data/disk0/vtune/bin64/support.txt file is absent? is it present?

This is issue of script that it fails in this place.

As workaround, you could add 'return None' to vtune/bin64/self_check.py script and rerun self checker again

    def get_build_number(self):
        try:
            support_path = self.get_support_path()
        except FileNotExistError as e:
            self.log.to_log("Cannot find 'support.txt' by path: %s" % e.path)
            return None

 

The 2nd issue with pax module. It is not connected with icelake at all. We try to investigate the reason, probably some kernel configuration and so on.

But did you try real vtune hardware collection such as 'Hardware Hotspots' and 'Microarchitecture Exploration'? We have driverless mode (VTune use perf, not VTune pax, sep drivers) and probably it will be applicable for you.

Kirill

 

0 Kudos
soderstrom__carl
1,466 Views

support.txt is not there

Yes I'm trying to use hw mode that's what I use on other processors. sw mode has not been working (I have another case about that #04651341)

Here's the cmdline I use

vtune -v -collect hotspots -knob sampling-mode=hw -knob sampling-interval=50 -knob enable-stack-collection=true -knob stack-size=0 -finalization-mode=none -data-limit=0 -run-pass-thru=--perf-compression=0 -run-pass-thru=--perf-aio=0 -result-dir $VTUNE_BASEDIR/result -target-pid $1 &

0 Kudos
MinYeol_L_Intel
Employee
1,453 Views

Regarding the pax driver loading issue, the driver does not use the symbol shown in dmesg. How did you compile the driver from source? Did you build it with the right kernel header that is matched with the kernel running on the system?

After I googled online, the issue could happen if you load the kernel module that was built against an older kernel than the kernel running on a system. Can you please check if that's the case?

 

Thanks,

 

0 Kudos
soderstrom__carl
1,422 Views

Hi -

Yes we traced it down to a compile tool chain issue. Once we got by that we could load the kernel mods. Then we got stuck on our vtune version not working with the "pre-production" Icelakes we are using. We downloaded the NDA version and I think we are all set.

We can close this case. Thanks

Reply