From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Doug Smythies <doug.smythies@gmail.com>, rjw@rjwysocki.net
Cc: dsmythies@telus.net, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [Resend][PATCH V2] cpufreq: intel_pstate: allow trace in passive mode
Date: Mon, 18 Dec 2017 15:30:57 -0800 [thread overview]
Message-ID: <1513639857.31113.12.camel@linux.intel.com> (raw)
In-Reply-To: <1513384980-3428-1-git-send-email-dsmythies@telus.net>
On Fri, 2017-12-15 at 16:43 -0800, Doug Smythies wrote:
> Allow use of the trace_pstate_sample trace function
> when the intel_pstate driver is in passive mode.
> Since the core_busy and scaled_busy fields are not
> used, and it might be desirable to know which path
> through the driver was used, either intel_cpufreq_target
> or intel_cpufreq_fast_switch, re-task the core_busy
> field as a flag indicator.
>
> The user can then use the intel_pstate_tracer.py utility
> to summarize and plot the trace.
>
> In Passive mode the driver is only called if there is
> a need to change the target frequency, so durations
> (time gaps between calls) can be very very long. The user
> needs to understand, and not be confused by, this limitation.
>
> V2: prepare for resend. Rebase to current kernel, 4.15-rc3.
> Signed-off-by: Doug Smythies <dsmythies@telus.net>
> ---
> drivers/cpufreq/intel_pstate.c | 50
> ++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 48 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/intel_pstate.c
> b/drivers/cpufreq/intel_pstate.c
> index 93a0e88..fe25d69 100644
> --- a/drivers/cpufreq/intel_pstate.c
> +++ b/drivers/cpufreq/intel_pstate.c
> @@ -1949,7 +1949,10 @@ static int intel_cpufreq_target(struct
> cpufreq_policy *policy,
> {
> struct cpudata *cpu = all_cpu_data[policy->cpu];
> struct cpufreq_freqs freqs;
> - int target_pstate;
> + struct sample *sample;
> + int target_pstate, from;
> + u64 time;
> + bool sample_taken;
>
> update_turbo_state();
>
> @@ -1969,12 +1972,32 @@ static int intel_cpufreq_target(struct
> cpufreq_policy *policy,
> break;
> }
> target_pstate = intel_pstate_prepare_request(cpu,
> target_pstate);
> +
> + from = cpu->pstate.current_pstate;
> + time = ktime_get();
> + sample_taken = intel_pstate_sample(cpu, time);
> +
This is quite a bit of overhead for tracing. Why not fold the above two
statements in the next if () with conditional tracing?
> if (target_pstate != cpu->pstate.current_pstate) {
> cpu->pstate.current_pstate = target_pstate;
> wrmsrl_on_cpu(policy->cpu, MSR_IA32_PERF_CTL,
> pstate_funcs.get_val(cpu,
> target_pstate));
> }
> freqs.new = target_pstate * cpu->pstate.scaling;
> +
> + if (sample_taken) {
if (trace_pstate_sample_enabled() && sample_taken) {
> + intel_pstate_calc_avg_perf(cpu);
> + sample = &cpu->sample;
> + trace_pstate_sample(0,
Not sure they are statement below are aligned correctly.
> + 0,
> + from,
> + cpu->pstate.current_pstate,
> + sample->mperf,
> + sample->aperf,
> + sample->tsc,
> + get_avg_frequency(cpu),
> + fp_toint(cpu->iowait_boost * 100));
> + }
> +
Same below in the intel_cpufreq_fast_switch().
Thanks,
Srinivas
next prev parent reply other threads:[~2017-12-18 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 0:43 [Resend][PATCH V2] cpufreq: intel_pstate: allow trace in passive mode Doug Smythies
2017-12-18 23:30 ` Srinivas Pandruvada [this message]
2017-12-19 0:24 ` Rafael J. Wysocki
2018-01-05 20:15 ` Doug Smythies
2018-01-05 21:06 ` Srinivas Pandruvada
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=1513639857.31113.12.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=doug.smythies@gmail.com \
--cc=dsmythies@telus.net \
--cc=linux-kernel@vger.kernel.org \
--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).