Skip to content

Commit

Permalink
Get GPUTracing lab script to listen to more user providers
Browse files Browse the repository at this point in the history
Now that EventEmitter.exe can emit UIforETW style events it makes
sense for lab scripts to listen for more providers. This adds all
of the Multi-* providers (EventEmitter.exe's odd naming scheme) plus
Microsoft-Windows-Win32k (Windows in focus, etc.) and the
controversial but maybe useful Microsoft-Windows-Kernel-Memory.

Flags are used to control exactly what is recorded, although
figuring out what they mean is yet another dark art.

How much this increases the data rate of the traces depends primarily
on how noisy EventEmitter.exe is.
  • Loading branch information
Bruce Dawson committed Oct 24, 2016
1 parent 180ce9d commit 22bd354
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion LabScripts/GPUTracing/start_tracing.bat
Expand Up @@ -21,7 +21,7 @@ set DX_Flags=DX:0x2F
@set SessionName=usersession
@set FileName=trace.etl
@set FileAndCompressFlags="%FileName%" -compress
@set UserProviders=%DX_Flags%
@set UserProviders=%DX_Flags%+Microsoft-Windows-Win32k:0xfdffffffefffffff+Multi-MAIN+Multi-FrameRate+Multi-Input+Multi-Worker+Microsoft-Windows-Kernel-Memory:0xE0

@rem Stop any previous tracing sessions that may have accidentally been left
@rem running. Otherwise the start command will fail with incredibly cryptic
Expand Down

0 comments on commit 22bd354

Please sign in to comment.