From: "Natarajan, Janakarajan" <Janakarajan.Natarajan@amd.com>
To: shuah <shuah@kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Thomas Renninger <trenn@suse.com>, Pu Wen <puwen@hygon.com>,
Borislav Petkov <bp@suse.de>,
Allison Randal <allison@lohutok.net>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Richard Fontana <rfontana@redhat.com>
Subject: Re: [PATCH 1/2] Modify cpupower to schedule itself on cores it is reading MSRs from
Date: Mon, 30 Sep 2019 15:34:09 +0000 [thread overview]
Message-ID: <251f40a6-9dd6-9611-ce77-b8eee4cf8fc8@amd.com> (raw)
In-Reply-To: <b90697df-e898-31d2-5149-c223cb11ba5c@kernel.org>
On 9/27/2019 1:59 PM, shuah wrote:
> On 9/18/19 10:34 AM, Natarajan, Janakarajan wrote:
>> Modify cpupower to schedule itself on each of the cpus in the system and
>> then get the APERF/MPERF register values.
>>
>> This is advantageous because an IPI is not generated when a
>> read_msr() is
>> executed on the local logical CPU thereby reducing the chance of having
>> APERF and MPERF being out of sync.
>
> Somehow this doesn't read right. Is this that you are trying to avoid
> APERF and MPERF being out of sync with this change?
>
> This description is rather confusing.
We are trying to avoid a separate IPI for APERF and MPERF. We have seen
that a separate IPI for
each can cause APERF and MPERF to go out of sync.
If the cpupower is already executing on the core it wants to get the
APERF/MPERF from, then
generic_exec_single() does not generate the IPI to execute the rdmsr().
Rather it just executes
on the current cpu.
I can change the description to add more detail.
>
>>
>> Signed-off-by: Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>
>> ---
>> .../utils/idle_monitor/mperf_monitor.c | 38 ++++++++++++++-----
>> 1 file changed, 28 insertions(+), 10 deletions(-)
>>
>> diff --git a/tools/power/cpupower/utils/idle_monitor/mperf_monitor.c
>> b/tools/power/cpupower/utils/idle_monitor/mperf_monitor.c
>> index 44806a6dae11..8b072e39c897 100644
>> --- a/tools/power/cpupower/utils/idle_monitor/mperf_monitor.c
>> +++ b/tools/power/cpupower/utils/idle_monitor/mperf_monitor.c
>> @@ -10,6 +10,7 @@
>> #include <stdlib.h>
>> #include <string.h>
>> #include <limits.h>
>> +#include <sched.h>
>> #include <cpufreq.h>
>> @@ -86,15 +87,33 @@ static int mperf_get_tsc(unsigned long long *tsc)
>> return ret;
>> }
>> +static int get_aperf_mperf(int cpu, unsigned long long *aval,
>> + unsigned long long *mval)
>> +{
>> + cpu_set_t set;
>> + int ret;
>> +
>> + CPU_ZERO(&set);
>> + CPU_SET(cpu, &set);
>> + if (sched_setaffinity(getpid(), sizeof(set), &set) == -1) {
>> + dprint("Could not migrate to cpu: %d\n", cpu);
>> + return 1;
>> + }
>> +
>> + ret = read_msr(cpu, MSR_APERF, aval);
>> + ret |= read_msr(cpu, MSR_MPERF, mval);
>> +
>> + return ret;
>> +}
>> +
>> static int mperf_init_stats(unsigned int cpu)
>> {
>> - unsigned long long val;
>> + unsigned long long aval, mval;
>> int ret;
>> - ret = read_msr(cpu, MSR_APERF, &val);
>> - aperf_previous_count[cpu] = val;
>> - ret |= read_msr(cpu, MSR_MPERF, &val);
>> - mperf_previous_count[cpu] = val;
>> + ret = get_aperf_mperf(cpu, &aval, &mval);
>
> get_aperf_mperf() could return error right? It returns 1 when
> sched_setaffinity() fails. Shouldn't the return value checked,
> instead of using aval and mval?
We set the is_valid[cpu] to the return value. Later on the is_valid[cpu]
is checked before proceeding to calculate the effective freq.
Thanks.
>
>> + aperf_previous_count[cpu] = aval;
>> + mperf_previous_count[cpu] = mval;
>> is_valid[cpu] = !ret;
>> return 0;
>> @@ -102,13 +121,12 @@ static int mperf_init_stats(unsigned int cpu)
>> static int mperf_measure_stats(unsigned int cpu)
>> {
>> - unsigned long long val;
>> + unsigned long long aval, mval;
>> int ret;
>> - ret = read_msr(cpu, MSR_APERF, &val);
>> - aperf_current_count[cpu] = val;
>> - ret |= read_msr(cpu, MSR_MPERF, &val);
>> - mperf_current_count[cpu] = val;
>> + ret = get_aperf_mperf(cpu, &aval, &mval);
>
> Same comments as above here.
>
>> + aperf_current_count[cpu] = aval;
>> + mperf_current_count[cpu] = mval;
>> is_valid[cpu] = !ret;
>> return 0;
>>
>
> thanks,
> -- Shuah
prev parent reply other threads:[~2019-09-30 15:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 16:34 Natarajan, Janakarajan
2019-09-18 16:34 ` [PATCH 2/2] Update cpupower to use the RDPRU instruction Natarajan, Janakarajan
2019-09-27 16:07 ` [PATCH 1/2] Modify cpupower to schedule itself on cores it is reading MSRs from Natarajan, Janakarajan
2019-09-27 21:48 ` Thomas Renninger
2019-10-02 14:45 ` Natarajan, Janakarajan
2019-10-05 12:40 ` Thomas Renninger
2019-10-07 21:11 ` Natarajan, Janakarajan
2019-10-10 11:22 ` Thomas Renninger
2019-10-11 16:58 ` Natarajan, Janakarajan
2019-09-27 18:59 ` shuah
2019-09-30 15:34 ` Natarajan, Janakarajan [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=251f40a6-9dd6-9611-ce77-b8eee4cf8fc8@amd.com \
--to=janakarajan.natarajan@amd.com \
--cc=allison@lohutok.net \
--cc=bp@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=puwen@hygon.com \
--cc=rfontana@redhat.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=trenn@suse.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
all inboxes | Powered by JetHome®