From: kernel test robot <lkp@intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
"Gautham R . Shenoy" <gautham.shenoy@amd.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Perry Yuan <perry.yuan@amd.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>,
"open list:CPU FREQUENCY SCALING FRAMEWORK"
<linux-pm@vger.kernel.org>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH] cpufreq/amd-pstate: Cache the max frequency in cpudata
Date: Sat, 14 Mar 2026 17:55:02 +0100 [thread overview]
Message-ID: <202603141750.mDER1GM9-lkp@intel.com> (raw)
In-Reply-To: <20260312182442.3236386-1-mario.limonciello@amd.com>
Hi Mario,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on rafael-pm/bleeding-edge linus/master v6.16-rc1 next-20260313]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Mario-Limonciello/cpufreq-amd-pstate-Cache-the-max-frequency-in-cpudata/20260314-194005
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20260312182442.3236386-1-mario.limonciello%40amd.com
patch subject: [PATCH] cpufreq/amd-pstate: Cache the max frequency in cpudata
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260314/202603141750.mDER1GM9-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260314/202603141750.mDER1GM9-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202603141750.mDER1GM9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/cpufreq/amd-pstate.c:1092:20: warning: variable 'perf' set but not used [-Wunused-but-set-variable]
1092 | union perf_cached perf;
| ^
1 warning generated.
vim +/perf +1092 drivers/cpufreq/amd-pstate.c
ec4e3326a95507 Huang Rui 2021-12-24 1082
ec4e3326a95507 Huang Rui 2021-12-24 1083 /*
ec4e3326a95507 Huang Rui 2021-12-24 1084 * This frequency is to indicate the maximum hardware frequency.
ec4e3326a95507 Huang Rui 2021-12-24 1085 * If boost is not active but supported, the frequency will be larger than the
ec4e3326a95507 Huang Rui 2021-12-24 1086 * one in cpuinfo.
ec4e3326a95507 Huang Rui 2021-12-24 1087 */
ec4e3326a95507 Huang Rui 2021-12-24 1088 static ssize_t show_amd_pstate_max_freq(struct cpufreq_policy *policy,
ec4e3326a95507 Huang Rui 2021-12-24 1089 char *buf)
ec4e3326a95507 Huang Rui 2021-12-24 1090 {
009d1c29a45194 Mario Limonciello 2025-01-17 1091 struct amd_cpudata *cpudata;
009d1c29a45194 Mario Limonciello 2025-01-17 @1092 union perf_cached perf;
ec4e3326a95507 Huang Rui 2021-12-24 1093
009d1c29a45194 Mario Limonciello 2025-01-17 1094 cpudata = policy->driver_data;
009d1c29a45194 Mario Limonciello 2025-01-17 1095 perf = READ_ONCE(cpudata->perf);
ec4e3326a95507 Huang Rui 2021-12-24 1096
a6b5fc5470a623 Mario Limonciello 2026-03-12 1097 return sysfs_emit(buf, "%u\n", cpudata->max_freq);
ec4e3326a95507 Huang Rui 2021-12-24 1098 }
ec4e3326a95507 Huang Rui 2021-12-24 1099
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-03-14 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 18:24 [PATCH] cpufreq/amd-pstate: Cache the max frequency in cpudata Mario Limonciello
2026-03-14 16:55 ` kernel test robot [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=202603141750.mDER1GM9-lkp@intel.com \
--to=lkp@intel.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mario.limonciello@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=perry.yuan@amd.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