From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EEA858615A for ; Tue, 14 Jan 2025 14:53:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736866407; cv=none; b=OwCPQrI+H/xKINVKo0eZIIdFXChwEj9e7cLZ+Q2zb7wfSJ+T8WEM+9Bu1OoE/Cfrr5Qg4TUa0+mYskSOSf7RAEE9UENZcGcG9A4diIkW8VYD1TzocN8JeDNc4IDWwy328adnvtncSj2LK32JZ3cDamGKIkcoXBRh9iwGnkkjWFk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736866407; c=relaxed/simple; bh=9A2D5ObTly72dQc3uXNt3Ia2rhh/O65dN4eJd77lLQg=; h=Message-ID:Date:From:To:Cc:Subject; b=ubqMpjJ5x9Ra/r1aJWu3+Mjeon6zqaX7fo8Jqf7IEJkPCs0EOP1tJEbjzDUMUUBpLJZHkUzf8AUooOtQgTNk+PniEL4wbXJdcNIo8O8DCS7Ul+mDi94QJePjsBFR2ZjovdOzqLiaDiB1cn3/bg9VQlDOk3B8SeDY9ESibJMXymA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 Received: by smtp.kernel.org (Postfix) with ESMTPSA id 84858C4CEE1; Tue, 14 Jan 2025 14:53:26 +0000 (UTC) Received: from rostedt by gandalf with local (Exim 4.98) (envelope-from ) id 1tXiIJ-00000000Fom-39uR; Tue, 14 Jan 2025 09:53:27 -0500 Message-ID: <20250114145313.452899098@goodmis.org> User-Agent: quilt/0.68 Date: Tue, 14 Jan 2025 09:53:13 -0500 From: Steven Rostedt To: linux-kernel@vger.kernel.org Cc: Masami Hiramatsu , Mark Rutland , Mathieu Desnoyers , Andrew Morton Subject: [for-linus][PATCH 0/2] tracing: Fixes for 6.13 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Tracing fixes for 6.13: - Fix a regression in the irqsoff and wakeup latency tracing The function graph tracer infrastructure has become generic so that kretprobes and BPF can be based on it. As it use to only handle function graph tracing, it would always calculate the time the function entered so that it could then calculate the time it exits and give the length of time the function executed for. But this is not needed for the other users (kretprobes and BPF) and the reading the clock adds a non-negligible overhead, so the calculation was moved into the function graph tracer logic. But the irqsoff and wakeup latency tracers, when the "display-graph" option was set, would use the function graph tracer to calculate the times of functions during the latency. The movement of the calltime calculation made the value zero for these tracers, and the output no longer showed the length of time of each tracer, but instead the absolute timestamp of when the function returned (rettime - calltime where calltime is zero). Have the irqsoff and wakeup latency tracers also do the calltime calculation as the function graph tracer does. - Update the tracing display to reflect the new preempt lazy model When the system is configured with preempt lazy, the output of the trace data would state "unknown" for the current preemption model. Because the lazy preemption model was just added, make it known to the tracing subsystem too. git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git trace/fixes Head SHA1: 24e0e610400aa2c765ee87b1b3c1401732b20fc5 Shrikanth Hegde (1): tracing: Print lazy preemption model Steven Rostedt (1): tracing: Fix irqsoff and wakeup latency tracers when using function graph ---- kernel/trace/trace.c | 1 + kernel/trace/trace_irqsoff.c | 14 ++++++++++++++ kernel/trace/trace_sched_wakeup.c | 14 ++++++++++++++ 3 files changed, 29 insertions(+)