Community
cancel
Showing results for 
Search instead for 
Did you mean: 
hongbor
Beginner
67 Views

vtsaview does not show data for module

Hello,

I tried ptu30_004_win_intel64 with the following commands. Vtsarun is fine. But vtsaview seems to show only the data for the entire run, not for specific module as specified in the command line. Any idea?


E:PerfGateTestsDXinamd64>set experiment_dir=utc-6536-1

E:PerfGateTestsDXinamd64>set path= oolsptu30_004_win_intel64in; oolsptu30_004_win_intel64in; oolsptu30_004_win_intel64in; oolsptu30_004_win_intel64in; oolsptu30_004_win_intel64in; oolsptu30_004_win_intel64in; oolsptu30_004_win_intel64in; oolsptu30_004_win_intel64in; oolsptu30_004_win_intel64in;e: oolsLiveViewBIN64;E:Perl;E:Perlin;E:Windowssystem32;E:Windows;E:WindowsSystem32Wbem;E:WindowsSystem32WindowsPowerShellv1.0;E:PerfGateTools;E:Debuggers;E:perlin;E:PerfGateTools;E:PerfGateToolsxperf;

E:PerfGateTestsDXinamd64>set configFile=E:Usershongbor.REDMONDworkspace.metadata.pluginscom.intel.ptu.filesearchsearchdirs.xml

E:PerfGateTestsDXinamd64>vtsarun.exe utc-6536-1 -s -ec CPU_CLK_UNHALTED.CORE:sa=1000000,INST_RETIRED.ANY:sa=1000000 -- autoshell.exe geometry9.xml
===== RUN 1 =====

Duration (sec): 0
Events configuration:

"CPU_CLK_UNHALTED.CORE":sa=1000000
"INST_RETIRED.ANY":sa=1000000

Data file: E:PerfGateTestsDXinamd64utc-6536-1ebs1206581178

Workload: autoshell.exe geometry9.xml

-----------------

profiling started => 3/26/2008 6:26:20 PM
workload started => 3/26/2008 6:26:20 PM
--- workload ---
Timestamp##Wed Mar 26 18:26:20 2008

Computer Name##HONGBOR-DXUTC

Processor Name##Intel Core2 CPU 6320 @ 1.86GHz

Processor Speed##1862

Number of Processors##1

RAM (Mb)##2034

BuildLab##6536.fbl_tools_phoenix(corevc).080215-1330-LDDM

OS Version##6.100

OS Build Number##6536.150

DX Interface##9.000

Adapter Name##Intel G965 Express Chipset Family

DeviceID##10658

VendorID##32902

Driver Name##igdumd64.dll

Driver Version##7.14.10.1283

DDI##9

DX Build##904.000

DX Version##9.000

DX Debug##false

PSGP Enabled##true

PerfX9{64}.dll##.

Geometry9{64}.dll##.

Adapter##D3DADAPTER_DEFAULT

DeviceType##D3DDEVTYPE_HAL

BehaviorFlags##D3DCREATE_HARDWARE_VERTEXPROCESSING

Windowed##TRUE

Window Dimension##{ 160, 120 }

Format##D3DFMT_A8R8G8B8

Start: uTLTextureSphereVS 1_1, TUID=Dx3DTESTTYPE_GEOMETRY64

Domain State##4108##0

BehaviorFlags##324##D3DCREATE_SOFTWARE_VERTEXPROCESSING

FPS##2120##41.890

Elapsed Cycles##1073741896##9378906929

Elapsed Time (s)##1073741896##5.03700733

Number Frames##72##211

AvgFPS##8##42.029

AvgFPS(StdDev)##8##0.346

Cycles Per Frame##1073741896##44449796.000

Cost (ms)##1073741896##23.87207222

Total Elapsed Cycles##1073741896##9378906929

Total Elapsed Time (s)##1073741896##5.037

Total Noise Cycles##1073741832##0

Total Noise Elapsed Time (s)##1073741896##0.000

Net Elapsed Cycles##1073741896##9378906929

Net Elapsed Time (s)##1073741896##5.037

Percent Noise##8## 0.000

Repeat Count##8##2

Geometry Processing (Megatriangles Per Sec)##8##18.675

Test passed.

End: Pass, uTLTextureSphereVS 1_1, TUID=0, Repro=E:PerfGateTestsDXinamd64autoshell.exe

Summary: Total=0, Passed=0, Failed=0, Blocked=0, Warned=0, Skipped=0

profiling finished => 3/26/2008 6:26:28 PM
--- workload ---
workload stopped => 3/26/2008 6:26:28 PM

E:PerfGateTestsDXinamd64>vtsaview.exe utc-6536-1 --convert --search-config E:Usershongbor.REDMONDworkspace.metadata.pluginscom.intel.ptu.filesearchsearchdirs.xml -granularity module --filter module,d3d9.dll
Intel Performance Tuning Utility version 3.0 build 860
Copyright (C) 2006-2007 Intel Corporation. All rights reserved

Software expires Apr. 1, 2008. 4 day(s) remain.

18:26:28.679 Loading data started
18:26:28.679 Performing file binding started
18:26:29.209 Performing file binding finished
18:26:29.334 Processing symbols started
18:26:29.334 Processing module 1 / 79 ()
18:26:29.334 Couldn't locate the file
18:26:29.334 Processing module 2 / 79 (ntoskrnl.exe)
18:26:29.428 Processing module 3 / 79 (hal.dll)
18:26:29.443 Processing module 4 / 79 (classpnp.sys)
18:26:29.459 Processing module 5 / 79 (iastorv.sys)
18:26:29.459 Processing module 6 / 79 (fltmgr.sys)
18:26:29.474 Processing module 7 / 79 (ndis.sys)
18:26:29.490 Processing module 8 / 79 (netio.sys)
18:26:29.506 Processing module 9 / 79 (cng.sys)
18:26:29.521 Processing module 10 / 79 (tcpip.sys)
18:26:29.537 Processing module 11 / 79 (ntfs.sys)
18:26:29.552 Processing module 12 / 79 (intelppm .sys)
18:26:29.568 Processing module 13 / 79 (igdkmd64.sys)
18:26:29.599 Processing module 14 / 79 (dxgkrnl.sys)
18:26:29.615 Processing module 15 / 79 (dxgmms1.sys)
18:26:29.630 Processing module 16 / 79 (watchdog.sys)
18:26:29.646 Processing module 17 / 79 (usbuhci.sys)
18:26:29.646 Processing module 18 / 79 (usbport.sys)
18:26:29.662 Processing module 19 / 79 (hdaudbus.sys)
18:26:29.677 Processing module 20 / 79 (npfs.sys)
18:26:29.677 Processing module 21 / 79 (afd.sys)
18:26:29.708 Processing module 22 / 79 (hidusb.sys)
18:26:29.724 Processing module 23 / 79 (hidclass.sys)
18:26:29.740 Processing module 24 / 79 (win32k.sys)
18:26:29.771 Processing module 25 / 79 (cdd.dll)
18:26:29.771 Processing module 26 / 79 (luafv.sys)
18:26:29.786 Processing module 27 / 79 (ntdll.dll)
18:26:29.849 Processing module 28 / 79 (ntdll.dll)
18:26:29.880 Processing module 29 / 79 (use r32.dll)
18:26:29.911 Processing module 30 / 79 (kernelbase.dll)
18:26:29.927 Processing module 31 / 79 (kernel32.dll)
18:26:29.958 Processing module 32 / 79 (msvcrt.dll)
18:26:29.989 Processing module 33 / 79 (rpcrt4.dll)
18:26:30.005 Processing module 34 / 79 (advapi32.dll)
18:26:30.036 Processing module 35 / 79 (apphelp.dll)
18:26:30.052 Processing module 36 / 79 (ole32.dll)
18:26:30.067 Processing module 37 / 79 (lsass.exe)
18:26:30.067 Processing module 38 / 79 (crypt32.dll)
18:26:30.083 Processing module 39 / 79 (shell32.dll)
18:26:30.145 Processing module 40 / 79 (mpengine.dll)
18:26:30.176 Processing module 41 / 79 (tdh.dll)
18:26:30.208 Processing module 42 / 79 (ikeext.dll)
18:26:30.223 Processing module 43 / 79 (jscript.dll)
18:26:30.239 Processing module 44 / 79 (sysmain.dll)
18:26:30.254 Processing module 45 / 79 (explorer.exe)
18:26:30.332 Processing module 46 / 79 (ieframe.dll)
18:26:30.457 Processing module 47 / 79 (wpdshserviceobj.dll)
18:26:30.457 Processing module 48 / 79 (mshtml.dll)
18:26:30.504 Processing module 49 / 79 (mstscax.dll)
18:26:30.520 Processing module 50 / 79 (jvm.dll)
18:26:30.566 Processing module 51 / 79 (swt-win32-3232.dll)
18:26:30.566 Couldn't load symbols from file e: oolsptu30_004_win_intel64eclipseconfigurationorg.eclipse.osgiundles981swt-win32-3232.dll
18:26:30.566 Processing module 52 / 79 (run_handler.dll)
18:26:30.598 Processing module 53 / 79 (kernel32.dll)
18:26:30.629 Processing module 54 / 79 (kernelbase.dll)
18:26:30.644 Processing module 55 / 79 (msvcrt.dll)
18:26:30.691 Processing module 56 / 79 (wttlog.dll)
18:26:30.691 Processing module 57 / 79 (advapi32.dll)
18:26:30.722 Processing module 58 / 79 (testx_core.dll)
18:26:32.236 Processing module 59 / 79 (gdi32.dll)
18:26:32.267 Processing module 60 / 79 (usp10.dll)
18:26:32.267 Processing module 61 / 79 (testx_utility.dll)
18:26:33.530 Processing module 62 / 79 (ole32 .dll)
18:26:33.562 Processing module 63 / 79 (oleaut32.dll)
18:26:33.577 Processing module 64 / 79 (testx_widget.dll)
18:27:02.999 Processing module 65 / 79 (msxml3.dll)
18:27:03.015 Processing module 66 / 79 (perfx9.dll)
18:27:03.296 Processing module 67 / 79 (testx_opengl.dll)
18:27:04.122 Processing module 68 / 79 (opengl32.dll)
18:27:04.138 Processing module 69 / 79 (testx_profile.dll)
18:27:06.213 Processing module 70 / 79 (testx_infosources.dll)
18:27:17.039 Processing module 71 / 79 (testx_d3d9.dll)
18:27:45.947 Processing module 72 / 79 (d3d9.dll)
18:27:45.962 Processing module 73 / 79 (igdumd64.dll)
18:27:45.993 Processing module 74 / 79 (geometry9.dll)
18:27:47.787 Processing module 75 / 79 (msvcp60.dll)
18:27:47.865 Processing module 76 / 79 (vtsa_gen.dll)
18:27:47.865 Processing module 77 / 79 (eventbase.dll)
18:27:47.881 Processing module 78 / 79 (xerces-c_2_7_em64t.dll)&n bsp;
18:27:48.146 Processing module 79 / 79 (msvcr80.dll)
18:27:48.177 Processing symbols finished
18:27:48.177 Processing basic blocks started
18:27:48.177 Processing module 1 / 10 ()
18:27:48.177 Couldn't locate the file
18:27:48.177 Processing module 2 / 10 (ntoskrnl.exe)
18:27:49.067 Processing module 3 / 10 (igdkmd64.sys)
18:27:49.269 Processing module 4 / 10 (dxgmms1.sys)
18:27:49.316 Processing module 5 / 10 (ntdll.dll)
18:27:49.550 Processing module 6 / 10 (msvcrt.dll)
18:27:49.706 Processing module 7 / 10 (testx_core.dll)
18:27:51.500 Processing module 8 / 10 (testx_widget.dll)
18:28:21.671 Processing module 9 / 10 (d3d9.dll)
18:28:21.921 Processing module 10 / 10 (igdumd64.dll)
18:28:22.404 Processing basic blocks finished
18:28:22.404 Loading data finished
18:28:22.467 Writing database started
18:28:22.669 Writing database finished
18:28:22.669 Viewing the data started

Event Based Sampling
Total samples: 33,578
User samples: 30,907
Kernel samples: 2,671

Events:
CPU_CLK_UNHALTED.CORE (Rate: 1000000)
Total samples: 12,427
User samples: 10,893
Kernel samples: 1,534

INST_RETIRED.ANY (Rate: 1000000)
Total samples: 21,151
User samples: 20,014
Kernel samples: 1,137

18:28:22.701 Viewing the data finished

thanks

rong

0 Kudos
1 Reply
Thomas_W_Intel
Employee
67 Views

Rong,

To me it looks like PTU wasn't able to identify your binary (""). This usually happens to me for virtual machines like Java or Python. Is autoshell.exe something similar?

Best regards

Thomas

Reply