From: Doug Smythies <dsmythies@telus.net>
To: Pratik Rajesh Sampat <psampat@linux.ibm.com>
Cc: rjw@rjwysocki.net, Daniel Lezcano <daniel.lezcano@linaro.org>,
shuah@kernel.org, ego@linux.vnet.ibm.com, svaidy@linux.ibm.com,
Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-kselftest@vger.kernel.org, pratik.r.sampat@gmail.com,
dsmythies <dsmythies@telus.net>
Subject: Re: [RFC v4 1/2] cpuidle: Extract IPI based and timer based wakeup latency from idle states
Date: Sun, 25 Apr 2021 13:47:10 -0700 [thread overview]
Message-ID: <CAAYoRsVcVnrBSNu=umdVWtRw3PyuD=c4uaCCcoGQpSWgq3AH=g@mail.gmail.com> (raw)
In-Reply-To: <20210412074309.38484-2-psampat@linux.ibm.com>
Hi Pratik,
On Mon, Apr 12, 2021 at 12:43 AM Pratik Rajesh Sampat
<psampat@linux.ibm.com> wrote:
>
> Introduce a mechanism to fire directed IPIs from a specified source CPU
> to a specified target CPU and measure the difference in time incurred on
> wakeup.
>
> Also, introduce a mechanism to queue a HR timer on a specified CPU and
> subsequently measure the time taken to wakeup the CPU.
>
> Finally define a simple debugfs interface to control the knobs to fire
> the IPI and Timer events on specified CPU and view their incurred idle
> wakeup latencies.
>
> Signed-off-by: Pratik Rajesh Sampat <psampat@linux.ibm.com>
Reviewed-by: Doug Smythies <dsmythies@telus.net>
next prev parent reply other threads:[~2021-04-25 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 7:43 [RFC v4 0/2] CPU-Idle latency selftest framework Pratik Rajesh Sampat
2021-04-12 7:43 ` [RFC v4 1/2] cpuidle: Extract IPI based and timer based wakeup latency from idle states Pratik Rajesh Sampat
2021-04-25 20:47 ` Doug Smythies [this message]
2021-04-12 7:43 ` [RFC v4 2/2] selftest/cpuidle: Add support for cpuidle latency measurement Pratik Rajesh Sampat
2021-04-25 20:49 ` Doug Smythies
2021-04-13 14:52 ` [RFC v4 0/2] CPU-Idle latency selftest framework Doug Smythies
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='CAAYoRsVcVnrBSNu=umdVWtRw3PyuD=c4uaCCcoGQpSWgq3AH=g@mail.gmail.com' \
--to=dsmythies@telus.net \
--cc=daniel.lezcano@linaro.org \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pratik.r.sampat@gmail.com \
--cc=psampat@linux.ibm.com \
--cc=rjw@rjwysocki.net \
--cc=shuah@kernel.org \
--cc=svaidy@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;
as well as URLs for NNTP newsgroup(s).