From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: rostedt@goodmis.org, mark.rutland@arm.com,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ftrace: print lazy preemption model
Date: Mon, 6 Jan 2025 22:24:44 +0900 [thread overview]
Message-ID: <20250106222444.28141b2b05cb4c7906f5e91e@kernel.org> (raw)
In-Reply-To: <20250103093647.575919-1-sshegde@linux.ibm.com>
On Fri, 3 Jan 2025 15:06:47 +0530
Shrikanth Hegde <sshegde@linux.ibm.com> wrote:
> Print lazy preemption model in ftrace header when latency-format=1.
>
> cat /sys/kernel/debug/sched/preempt
> none voluntary full (lazy)
>
> Without patch:
> latency: 0 us, #232946/232946, CPU#40 | (M:unknown VP:0, KP:0, SP:0 HP:0 #P:80)
> With Patch:
> latency: 0 us, #1897938/25566788, CPU#16 | (M:lazy VP:0, KP:0, SP:0 HP:0 #P:80)
>
Looks good to me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thanks,
> Signed-off-by: Shrikanth Hegde <sshegde@linux.ibm.com>
> ---
> kernel/trace/trace.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index f8aebcb01e62..b6e40e8791fa 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -4122,6 +4122,7 @@ print_trace_header(struct seq_file *m, struct trace_iterator *iter)
> preempt_model_none() ? "server" :
> preempt_model_voluntary() ? "desktop" :
> preempt_model_full() ? "preempt" :
> + preempt_model_lazy() ? "lazy" :
> preempt_model_rt() ? "preempt_rt" :
> "unknown",
> /* These are reserved for later use */
> --
> 2.39.3
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2025-01-06 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 9:36 Shrikanth Hegde
2025-01-06 13:24 ` Masami Hiramatsu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250106222444.28141b2b05cb4c7906f5e91e@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rostedt@goodmis.org \
--cc=sshegde@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®