From: "Hernandez Lopez, Fabiola" <fabiola.hernandez.lopez@intel.com>
To: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Frequency not returning to fixed value after AVX workload
Date: Fri, 11 Oct 2019 17:45:55 +0000 [thread overview]
Message-ID: <67737C20FC7E4D44B44817ABFA5B1DCE6EC01C77@CRSMSX104.amr.corp.intel.com> (raw)
Hi,
We are seeing an unexpected behavior after applying AVX workloads.
After setting the CPU frequency to a fixed value with CPU Freq - userspace governor and applying heavy AVX workloads, the CPU frequency is decreased (as expected) but it never returns to the previously established value. This does not happen on all cores, only on a single core. The only way to return to the desired frequency is by setting it through the command line again.
We are wondering how can this change in frequency happen.
Thanks,
Fabiola
next reply other threads:[~2019-10-11 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 17:45 Hernandez Lopez, Fabiola [this message]
2019-10-14 9:44 ` Frequency not returning to fixed value after AVX workload Rafael J. Wysocki
2019-10-14 21:11 ` Hernandez Lopez, Fabiola
2019-10-14 21:23 ` Srinivas Pandruvada
2019-10-23 18:26 ` Hernandez Lopez, Fabiola
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=67737C20FC7E4D44B44817ABFA5B1DCE6EC01C77@CRSMSX104.amr.corp.intel.com \
--to=fabiola.hernandez.lopez@intel.com \
--cc=linux-pm@vger.kernel.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).