diff --git a/client/TracySysTrace.hpp b/client/TracySysTrace.hpp
index b5933faf..6b1fc745 100644
--- a/client/TracySysTrace.hpp
+++ b/client/TracySysTrace.hpp
@@ -1,7 +1,7 @@
 #ifndef __TRACYSYSTRACE_HPP__
 #define __TRACYSYSTRACE_HPP__
 
-#if defined _WIN32 || defined __CYGWIN__ || defined __linux__
+#if !defined TRACY_NO_SYSTEM_TRACING && ( defined _WIN32 || defined __CYGWIN__ || defined __linux__ )
 #  define TRACY_HAS_SYSTEM_TRACING
 #endif
 
diff --git a/manual/tracy.tex b/manual/tracy.tex
index 44d4e4dd..10f0f1ad 100644
--- a/manual/tracy.tex
+++ b/manual/tracy.tex
@@ -1156,6 +1156,8 @@ 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.
+
 \begin{bclogo}[
 noborder=true,
 couleur=black!5,