Analyzers
Support for Analyzers (Intel VTune™ Profiler, Intel Advisor, Intel Inspector)
Announcements
This community is designed for sharing of public information. Please do not share Intel or third-party confidential information here.
4679 Discussions

Process name not getting diaplayed

Poornima_N_Intel
Employee
152 Views

Hi,

I'm observing the vtune data being displayed as pid0x0 instead of the process name in some 5 sample , imported from the .tb6 file.

Any idea how to find out the name of the process corresponding to the pid id?

Thanks in advance.

 

0 Kudos
1 Solution
David_A_Intel1
Employee
152 Views

Is it pid 0x0 only?  pid 0x0 is a system process that handles idle time and, depending on the system, throttling CPU speed.

You can't take vmlinux from the data.0 directory.  If you want to resolve symbols for vmlinux, you need an uncompressed debug version of the kernel.  You don't have to be running it, but it must match the running kernel.  Then, configure VTune Amplifier's search directory to point to the directory containing the debug info and re-resolve.

View solution in original post

4 Replies
Peter_W_Intel
Employee
152 Views

I think that pid number is better than process name, if there are many processes running with same module name.

I tried to practice your need, attach a running process, use tb6 file to import vtune result directory...

# amplxe-cl -collect advanced-hotspots -d 30 -target-pid 21486

# amplxe-cl -import tbs2034690867.tb6 -r ../../r017   (should go to result directory, then find tb6 file under .data0 sub-directory)

# amplxe-cl -report hw-events -group-by process -r r017 (go back to ../..r017)

Then you can see data like this format:

Process                  Hardware Event Count:CPU_CLK_UNHALTED.THREAD:Self (K)  Hardware Event Count:CPU_CLK_UNHALTED.REF_TSC:Self (K)  Hardware Event Count:INST_RETIRED.ANY:Self (K)
-----------------------  -----------------------------------------------------  ------------------------------------------------------  ----------------------------------------------

 

 

vmlinux                                                                 377400                                                  518000                                           95200
amplxe-runss                                                             64600                                                   82000                                           20400
wnck-applet                                                              34000                                                   24000                                            6800
Xvnc                                                                     17000                                                   26000                                               0
gnome-terminal                                                           13600                                                   40000                                               0
firefox                                                                  10200                                                    8000                                               0

 

 

 

Poornima_N_Intel
Employee
152 Views

One more point to add, to get the process name I copied  vmlinux binary in data.0 folder and then did a re-resolve.

But loading is getting failed. Is this the reason for the process name not getting displayed?.

 

David_A_Intel1
Employee
153 Views

Is it pid 0x0 only?  pid 0x0 is a system process that handles idle time and, depending on the system, throttling CPU speed.

You can't take vmlinux from the data.0 directory.  If you want to resolve symbols for vmlinux, you need an uncompressed debug version of the kernel.  You don't have to be running it, but it must match the running kernel.  Then, configure VTune Amplifier's search directory to point to the directory containing the debug info and re-resolve.

Bernard
Black Belt
152 Views

>>>  pid 0x0 is a system process that handles idle time and, depending on the system, throttling CPU speed>>>

On Windows OS system idle proces probably runs Nt!KeIdleLoop where there is no thread to be run on the specific core.

Reply