From: Viresh Kumar <viresh.kumar@linaro.org>
To: Andy Tang <andy.tang@nxp.com>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [EXT] Re: Ask for help about cpufreq issue
Date: Mon, 17 Feb 2020 13:52:00 +0530 [thread overview]
Message-ID: <20200217082200.nedwl4fa7byc54za@vireshk-i7> (raw)
In-Reply-To: <VI1PR04MB4333A771266A447FB8682E2FF3150@VI1PR04MB4333.eurprd04.prod.outlook.com>
On 14-02-20, 10:00, Andy Tang wrote:
> From cs_dbs_update() function, I did see that sometimes the LOAD is at 100% usage.
> There is almost no application running. That must be some spikes of working running.
> Unfortunately I can't track them by cs_dbs_update() or ftrace tool.
> I doubt the ftrace can be used this way. Do you have any other suggestions? Maybe another tools?
Not sure if you used ftrace correctly, do following steps:
Enable following options in kernel config and rebuild your image.
- CONFIG_FTRACE
- CONFIG_FUNCTION_TRACER
and then run this script at runtime.
-------------------------8<-------------------------
#!/bin/bash
# Locals
BUFFER=40000
FILE="dft"
# What to trace ??
#EVENTS=" -e sched -e power -e workqueue -e irq"
EVENTS="all"
echo "Starting trace"
/usr/bin/trace-cmd start -b $BUFFER $EVENTS
#You can run some test here that you want to trace.
sleep 5
/usr/bin/trace-cmd stop
cat /sys/kernel/debug/tracing/trace > $FILE.txt
/usr/bin/trace-cmd extract -o $FILE.dat
echo "Saved trace in: "$FILE
sync
-------------------------8<-------------------------
The output file here (dft.dat) can be opened with kernel-shark tool.
Your testing platform's userspace must have trace-cmd command for this to work.
--
viresh
prev parent reply other threads:[~2020-02-17 8:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 5:09 Ask for help about cpufreq issue Andy Tang
2020-02-07 5:23 ` Viresh Kumar
2020-02-07 6:03 ` [EXT] " Andy Tang
2020-02-07 7:05 ` Viresh Kumar
2020-02-11 4:20 ` Andy Tang
2020-02-11 5:53 ` Viresh Kumar
2020-02-11 6:23 ` Andy Tang
2020-02-11 6:34 ` Viresh Kumar
2020-02-11 7:20 ` Andy Tang
2020-02-12 10:11 ` Andy Tang
2020-02-12 11:50 ` Viresh Kumar
2020-02-13 8:18 ` Andy Tang
2020-02-13 8:48 ` Viresh Kumar
2020-02-13 9:12 ` Andy Tang
2020-02-13 9:15 ` Viresh Kumar
2020-02-13 9:21 ` Andy Tang
2020-02-14 10:00 ` Andy Tang
2020-02-17 8:22 ` Viresh Kumar [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=20200217082200.nedwl4fa7byc54za@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=andy.tang@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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