From: kernel test robot <lkp@intel.com>
To: aubrey.li@linux.intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [anolis-intel-cloud:devel-5.10 0/1] drivers/cpufreq/amd-pstate.c:104: warning: Function parameter or member 'req' not described in 'amd_cpudata'
Date: Sat, 20 Dec 2025 00:32:35 +0800 [thread overview]
Message-ID: <202512200014.uDRL9fG2-lkp@intel.com> (raw)
Hi Huang,
First bad commit (maybe != root cause):
tree: https://gitee.com/anolis/intel-cloud-kernel.git devel-5.10
head: 7d06d639106cda70074fdaa0e0910c92274e47fc
commit: d86c89cda7bc4b35fa412bc53f8656eeee39a73c [0/1] cpufreq: amd-pstate: Add boost mode support for AMD P-State
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20251220/202512200014.uDRL9fG2-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 1335a05ab8bc8339ce24be3a9da89d8c3f4e0571)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251220/202512200014.uDRL9fG2-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/202512200014.uDRL9fG2-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/cpufreq/amd-pstate.c:104: warning: Function parameter or member 'req' not described in 'amd_cpudata'
>> drivers/cpufreq/amd-pstate.c:104: warning: Function parameter or member 'boost_supported' not described in 'amd_cpudata'
vim +104 drivers/cpufreq/amd-pstate.c
174aa8cb9d486e Huang Rui 2021-12-24 67
174aa8cb9d486e Huang Rui 2021-12-24 68 /**
174aa8cb9d486e Huang Rui 2021-12-24 69 * struct amd_cpudata - private CPU data for AMD P-State
174aa8cb9d486e Huang Rui 2021-12-24 70 * @cpu: CPU number
174aa8cb9d486e Huang Rui 2021-12-24 71 * @cppc_req_cached: cached performance request hints
174aa8cb9d486e Huang Rui 2021-12-24 72 * @highest_perf: the maximum performance an individual processor may reach,
174aa8cb9d486e Huang Rui 2021-12-24 73 * assuming ideal conditions
174aa8cb9d486e Huang Rui 2021-12-24 74 * @nominal_perf: the maximum sustained performance level of the processor,
174aa8cb9d486e Huang Rui 2021-12-24 75 * assuming ideal operating conditions
174aa8cb9d486e Huang Rui 2021-12-24 76 * @lowest_nonlinear_perf: the lowest performance level at which nonlinear power
174aa8cb9d486e Huang Rui 2021-12-24 77 * savings are achieved
174aa8cb9d486e Huang Rui 2021-12-24 78 * @lowest_perf: the absolute lowest performance level of the processor
174aa8cb9d486e Huang Rui 2021-12-24 79 * @max_freq: the frequency that mapped to highest_perf
174aa8cb9d486e Huang Rui 2021-12-24 80 * @min_freq: the frequency that mapped to lowest_perf
174aa8cb9d486e Huang Rui 2021-12-24 81 * @nominal_freq: the frequency that mapped to nominal_perf
174aa8cb9d486e Huang Rui 2021-12-24 82 * @lowest_nonlinear_freq: the frequency that mapped to lowest_nonlinear_perf
174aa8cb9d486e Huang Rui 2021-12-24 83 *
174aa8cb9d486e Huang Rui 2021-12-24 84 * The amd_cpudata is key private data for each CPU thread in AMD P-State, and
174aa8cb9d486e Huang Rui 2021-12-24 85 * represents all the attributes and goals that AMD P-State requests at runtime.
174aa8cb9d486e Huang Rui 2021-12-24 86 */
174aa8cb9d486e Huang Rui 2021-12-24 87 struct amd_cpudata {
174aa8cb9d486e Huang Rui 2021-12-24 88 int cpu;
174aa8cb9d486e Huang Rui 2021-12-24 89
d86c89cda7bc4b Huang Rui 2021-12-24 90 struct freq_qos_request req[2];
174aa8cb9d486e Huang Rui 2021-12-24 91 u64 cppc_req_cached;
174aa8cb9d486e Huang Rui 2021-12-24 92
174aa8cb9d486e Huang Rui 2021-12-24 93 u32 highest_perf;
174aa8cb9d486e Huang Rui 2021-12-24 94 u32 nominal_perf;
174aa8cb9d486e Huang Rui 2021-12-24 95 u32 lowest_nonlinear_perf;
174aa8cb9d486e Huang Rui 2021-12-24 96 u32 lowest_perf;
174aa8cb9d486e Huang Rui 2021-12-24 97
174aa8cb9d486e Huang Rui 2021-12-24 98 u32 max_freq;
174aa8cb9d486e Huang Rui 2021-12-24 99 u32 min_freq;
174aa8cb9d486e Huang Rui 2021-12-24 100 u32 nominal_freq;
174aa8cb9d486e Huang Rui 2021-12-24 101 u32 lowest_nonlinear_freq;
d86c89cda7bc4b Huang Rui 2021-12-24 102
d86c89cda7bc4b Huang Rui 2021-12-24 103 bool boost_supported;
174aa8cb9d486e Huang Rui 2021-12-24 @104 };
174aa8cb9d486e Huang Rui 2021-12-24 105
:::::: The code at line 104 was first introduced by commit
:::::: 174aa8cb9d486ed632ed6d6bbbafe39306f1a7f7 cpufreq: amd-pstate: Introduce a new AMD P-State driver to support future processors
:::::: TO: Huang Rui <ray.huang@amd.com>
:::::: CC: Xunlei Pang <xlpang@linux.alibaba.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-19 16:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202512200014.uDRL9fG2-lkp@intel.com \
--to=lkp@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.