From: Prasad Sodagudi <psodagud@codeaurora.org>
To: rostedt@goodmis.org, tglx@linutronix.de, qais.yousef@arm.com,
peterz@infradead.org, mingo@kernel.org, cai@lca.pw,
tyhicks@canonical.com, arnd@arndb.de
Cc: rameezmustafa@codeaurora.org, linux-kernel@vger.kernel.org,
Prasad Sodagudi <psodagud@codeaurora.org>
Subject: [PATCH 0/2] measure latency of cpu hotplug path
Date: Wed, 23 Sep 2020 16:37:44 -0700 [thread overview]
Message-ID: <1600904266-102397-1-git-send-email-psodagud@codeaurora.org> (raw)
There are all changes related to cpu hotplug path and would like to seek
upstream review. These are all patches in Qualcomm downstream kernel
for a quite long time. First patch sets the rt prioity to hotplug
task and second patch adds cpuhp trace events.
1) cpu-hotplug: Always use real time scheduling when hotplugging a CPU
2) cpu/hotplug: Add cpuhp_latency trace event
Example logs:-
cpu online -
cpuhp/4-200 [004] .... 223.891886: cpuhp_enter: cpu: 0004 target: 213 step: 212 (sched_cpu_activate)
cpuhp/4-200 [004] .... 223.891894: cpuhp_exit: cpu: 0004 state: 212 step: 212 ret: 0
sh-176 [000] .... 223.891912: cpuhp_exit: cpu: 0004 state: 213 step: 86 ret: 0
sh-176 [000] .... 223.891915: cpuhp_latency: cpu:4 state:online latency:3874 USEC ret: 0
cpu offline -
sh-176 [000] .... 265.193490: cpuhp_exit: cpu: 0004 state: 2 step: 2 ret: 0
sh-176 [000] .... 265.193494: cpuhp_latency: cpu:4 state:offline latency:57431 USEC ret: 0
Prasad Sodagudi (1):
cpu/hotplug: Add cpuhp_latency trace event
Syed Rameez Mustafa (1):
cpu-hotplug: Always use real time scheduling when hotplugging a CPU
include/trace/events/cpuhp.h | 29 +++++++++++++++++++++++++
kernel/cpu.c | 50 ++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 79 insertions(+)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2020-09-23 23:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 23:37 Prasad Sodagudi [this message]
2020-09-23 23:37 ` [PATCH 1/2] cpu/hotplug: Add cpuhp_latency trace event Prasad Sodagudi
2020-09-28 14:58 ` Thomas Gleixner
2020-09-23 23:37 ` [PATCH 2/2] cpu-hotplug: Always use real time scheduling when hotplugging a CPU Prasad Sodagudi
2020-09-24 8:34 ` [PATCH 0/2] measure latency of cpu hotplug path peterz
2020-09-24 14:58 ` Steven Rostedt
2020-09-28 2:41 ` psodagud
2020-09-28 7:40 ` Peter Zijlstra
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=1600904266-102397-1-git-send-email-psodagud@codeaurora.org \
--to=psodagud@codeaurora.org \
--cc=arnd@arndb.de \
--cc=cai@lca.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=rameezmustafa@codeaurora.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tyhicks@canonical.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