From: peterz@infradead.org
To: Prasad Sodagudi <psodagud@codeaurora.org>
Cc: rostedt@goodmis.org, tglx@linutronix.de, qais.yousef@arm.com,
mingo@kernel.org, cai@lca.pw, tyhicks@canonical.com,
arnd@arndb.de, rameezmustafa@codeaurora.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] measure latency of cpu hotplug path
Date: Thu, 24 Sep 2020 10:34:14 +0200 [thread overview]
Message-ID: <20200924083414.GB1362448@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1600904266-102397-1-git-send-email-psodagud@codeaurora.org>
On Wed, Sep 23, 2020 at 04:37:44PM -0700, Prasad Sodagudi wrote:
> 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
Why? Hotplug is a known super slow path. If you care about hotplug
latency you're doing it wrong.
next prev parent reply other threads:[~2020-09-24 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 23:37 Prasad Sodagudi
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 ` peterz [this message]
2020-09-24 14:58 ` [PATCH 0/2] measure latency of cpu hotplug path 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=20200924083414.GB1362448@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arnd@arndb.de \
--cc=cai@lca.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=psodagud@codeaurora.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
all inboxes | Powered by JetHome®