From 22bd35488e03179449ae98bfed50e90c479ae0a4 Mon Sep 17 00:00:00 2001 From: Bruce Dawson Date: Sun, 23 Oct 2016 21:58:09 -0700 Subject: [PATCH] Get GPUTracing lab script to listen to more user providers 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. --- LabScripts/GPUTracing/start_tracing.bat | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/LabScripts/GPUTracing/start_tracing.bat b/LabScripts/GPUTracing/start_tracing.bat index fb55e8f2..ef6d9243 100644 --- a/LabScripts/GPUTracing/start_tracing.bat +++ b/LabScripts/GPUTracing/start_tracing.bat @@ -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