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: Thu, 13 Feb 2020 14:45:36 +0530 [thread overview]
Message-ID: <20200213091536.bwxyuwjzga4uogeb@vireshk-i7> (raw)
In-Reply-To: <VI1PR04MB4333FD2725CA091989CAC979F31A0@VI1PR04MB4333.eurprd04.prod.outlook.com>
On 13-02-20, 09:12, Andy Tang wrote:
> Hi Viresh,
>
> > -----Original Message-----
> > From: Viresh Kumar <viresh.kumar@linaro.org>
> > Sent: 2020年2月13日 16:48
> > To: Andy Tang <andy.tang@nxp.com>
> > Cc: rjw@rjwysocki.net; linux-pm@vger.kernel.org
> > Subject: Re: [EXT] Re: Ask for help about cpufreq issue
> >
> > I agree. Which means that there are some spikes of work getting scheduled
> > on CPUs. The load will increase slowly and will also decrease slowly
> > (step-by-step) with conservative governor.
> >
> > > So I can't understand why cpu frequency increased?
> >
> > Tracing or debugging cs_dbs_update() in conservative governor is the only
> > way out I would suggest.
> What's the *TRACING" here referring to? Could you please explain more about it?
> I have no idea what it is.
Sorry about that, I was talking about the in-kernel function tracer
here.
https://www.kernel.org/doc/Documentation/trace/ftrace.txt
--
viresh
next prev parent reply other threads:[~2020-02-13 9:15 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 [this message]
2020-02-13 9:21 ` Andy Tang
2020-02-14 10:00 ` Andy Tang
2020-02-17 8:22 ` Viresh Kumar
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=20200213091536.bwxyuwjzga4uogeb@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;
as well as URLs for NNTP newsgroup(s).