From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1499] Intel uncore power library fails because of too many frequencies
Date: Fri, 19 Jul 2024 22:29:21 +0000 [thread overview]
Message-ID: <bug-1499-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1499
Bug ID: 1499
Summary: Intel uncore power library fails because of too many
frequencies
Product: DPDK
Version: 24.07
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Running 24.07-rc2 on Intel core box fails the power uncore test because:
RTE>>power_intel_uncore_autotest
POWER: Too many available uncore frequencies: 33
POWER: Cannot get available uncore frequencies of pkg 00 die 00
Cannot initialise uncore power management for pkg 0 die 0, this may occur if
environment is not configured correctly(APCI cpufreq) or operating in another
valid Power management environment
The CPU is: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
initial_max_freq_khz:3600000
initial_min_freq_khz:400000
max_freq_khz:3600000
min_freq_khz:400000
Which leads to this expression:
num_uncore_freqs = (ui->init_max_freq - ui->init_min_freq) / BUS_FREQ +
1;
if (num_uncore_freqs >= MAX_UNCORE_FREQS) {
POWER_LOG(ERR, "Too many available uncore frequencies: %d",
num_uncore_freqs);
I.e:
num_uncore_freqs = (3600000 - 400000) / 100000 + 1
= 33
Looks like an off-by-one error, was this ever tested?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3528 bytes --]
next reply other threads:[~2024-07-19 22:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 22:29 bugzilla [this message]
2024-07-30 8:01 ` bugzilla
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=bug-1499-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).