mirror of
https://github.com/wolfpld/tracy.git
synced 2024-11-10 02:31:48 +00:00
Allow disabling context switch tracing.
Currently only on Windows.
This commit is contained in:
parent
a34abe646c
commit
4caaa325c2
@ -368,7 +368,10 @@ bool SysTraceStart( int64_t& samplingPeriod )
|
||||
const auto psz = sizeof( EVENT_TRACE_PROPERTIES ) + sizeof( KERNEL_LOGGER_NAME );
|
||||
s_prop = (EVENT_TRACE_PROPERTIES*)tracy_malloc( psz );
|
||||
memset( s_prop, 0, sizeof( EVENT_TRACE_PROPERTIES ) );
|
||||
ULONG flags = EVENT_TRACE_FLAG_CSWITCH | EVENT_TRACE_FLAG_DISPATCHER | EVENT_TRACE_FLAG_THREAD;
|
||||
ULONG flags = 0;
|
||||
#ifndef TRACY_NO_CONTEXT_SWITCH
|
||||
flags = EVENT_TRACE_FLAG_CSWITCH | EVENT_TRACE_FLAG_DISPATCHER | EVENT_TRACE_FLAG_THREAD;
|
||||
#endif
|
||||
if( isOs64Bit ) flags |= EVENT_TRACE_FLAG_PROFILE;
|
||||
s_prop->EnableFlags = flags;
|
||||
s_prop->LogFileMode = EVENT_TRACE_REAL_TIME_MODE;
|
||||
|
@ -1743,7 +1743,7 @@ As a corollary, it is often not enough to know how long it took to execute a zon
|
||||
|
||||
To solve this problem, Tracy collects context switch\footnote{A context switch happens when any given CPU core stops executing one thread and starts running another one.} information. This data can be then used to see when a zone was in the executing state and where it was waiting to be resumed.
|
||||
|
||||
Context switch data capture may be disabled by adding the \texttt{TRACY\_NO\_SYSTEM\_TRACING} define to the client.
|
||||
Context switch data capture may be disabled by adding the \texttt{TRACY\_NO\_CONTEXT\_SWITCH} define to the client. Alternatively, the \texttt{TRACY\_NO\_SYSTEM\_TRACING} define may be used to disable all tracing needing privilege escalation.
|
||||
|
||||
\begin{bclogo}[
|
||||
noborder=true,
|
||||
|
Loading…
Reference in New Issue
Block a user