From cec95341ec92fe2001ad1eaec6634b97003deadb Mon Sep 17 00:00:00 2001 From: Luca Ceresoli Date: Mon, 13 Jan 2025 11:25:31 +0100 Subject: [PATCH] debugging: labs: tweak mystery_program timings to be more visible over shared video The 200 ms timing produces a short pause in crc_random, probably not very visible over shared video for trainees with low bandwidth. Signed-off-by: Luca Ceresoli --- .../debugging-system-wide-profiling.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex b/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex index 265c537082..53938ec55c 100644 --- a/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex +++ b/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex @@ -12,7 +12,7 @@ \section{ftrace \& uprobes} First of all, we will start a small program on the target using the following command: \begin{bashinput} -$ mystery_program 1000 200 2 & +$ mystery_program 1500 400 2 & \end{bashinput} In order to trace a full system, we can use ftrace. However, if we want to trace