From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [Query] How to measure the entry-latency-us and exit-latency-us on arm PSCI system
Date: Mon, 16 Nov 2015 20:10:55 +0800 [thread overview]
Message-ID: <20151116201055.00567e90@xhacker> (raw)
Hi all,
Now, I'd like to add cpuidle support to Marvell berlin arm64 soc via
drivers/cpuidle/dt_idle_states.c. The system is PSCI-1.0 compatible.
Per my understanding:
The entry-latency-us: the time from beginning of cpuidle_idle_call()
to the firmware's last WFI instruction. Should test more times to find
the longest time.
The exit-latency-us: the time from the first instruction of waken up cpu
to the end of cpuidle_idle_call(). Should test more times to find the longest
time.
If cpufreq is available, we should fix the cpufreq to the lowest freq to do
the above test.
Even I have a look at idle-states binding doc, I'm still not sure whether my
solution to measure the entry-latency-us and exit-latency-us is correct or not,
could you please give suggestions?
Thanks in advance,
Jisheng
next reply other threads:[~2015-11-16 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 12:10 Jisheng Zhang [this message]
2015-11-16 16:05 ` [Query] How to measure the entry-latency-us and exit-latency-us on arm PSCI system Lorenzo Pieralisi
2015-11-17 3:56 ` Jisheng Zhang
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=20151116201055.00567e90@xhacker \
--to=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).