DPDK usage discussions
 help / color / mirror / Atom feed
From: "Xiaoping Yan (NSB)" <xiaoping.yan@nokia-sbell.com>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: RE: dpdk-test power_autotest, power_caps_autotest
Date: Wed, 11 Jan 2023 11:52:27 +0000	[thread overview]
Message-ID: <4980d4729a204e2c9fa2e31f6a297087@nokia-sbell.com> (raw)
In-Reply-To: <CAO8pfFmWSrSE51tcmbK3nxpJo4C==uCRh7oGPU0s5C2if=+XxA@mail.gmail.com>

Hi,

Have you checked if the file exist in your system (replace the %u with a cpu index)
/sys/devices/system/cpu/cpu%u/cpufreq/scaling_governor

Also write to above file requires root user.

-----Original Message-----
From: Antonio Di Bacco <a.dibacco.ks@gmail.com> 
Sent: 2023年1月11日 18:06
To: users@dpdk.org
Subject: dpdk-test power_autotest, power_caps_autotest

The dpdk-test is really a nice piece of software.
Today I tried to use it to "autotest" the power DPDK subsystem but I fail to fully understand the feedback it gives (consider I've disable intel_pstate driver):

For example:

RTE>>power_autotest
POWER: Invalid Power Management Environment(0) set


RTE>>power_caps_autotest
POWER: Env isn't set yet!
POWER: Attempting to initialise ACPI cpufreq power management...
POWER: Failed to write /sys/devices/system/cpu/cpu%u/cpufreq/scaling_governor
POWER: Cannot set governor of lcore 2 to userspace
POWER: Attempting to initialise PSTAT power management...
POWER: Initialized successfully for lcore 2 power management
POWER: Capabilities 1


How to fix the "Invalid Power Management Environment(0) set" and the Failed to write /sys/devices/system/cpu/cpu%u/cpufreq/scaling_governor
?

      reply	other threads:[~2023-01-11 11:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 10:05 Antonio Di Bacco
2023-01-11 11:52 ` Xiaoping Yan (NSB) [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=4980d4729a204e2c9fa2e31f6a297087@nokia-sbell.com \
    --to=xiaoping.yan@nokia-sbell.com \
    --cc=a.dibacco.ks@gmail.com \
    --cc=users@dpdk.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).